Slashdot Mirror
Details On IE7 CSS Changes
writes "IE development team has released a list of CSS changes for IE7. Some of the notable new features are enabling :hover for all elements, and implementing position:fixed, and PNG transparency support. In addition, there is a long list of fixed bugs that plagued previous IE browsers for years. These changes (except for PNG transparency) only work under the <!DOCTYPE> switch to preserve compatibility with previous versions of IE."
that IE blog post is from August.
Old News.
It's about damn time. No more having to use crappy file formats to make sure that your websites have to work with IE anymore.
At least, to some extent.
Will I have to unfix or re-fix all my PNG transaprency Javascript to compensate for the turd that is IE7?
Polish it! Make it Shiny! Microsoft brand turd-polish.
meh
It's too bad they couldn't be bothered to add support for CSS opacity then. All the other major browsers have supported that forever, and using filter:alpha(opacity) is getting stupid.
Also the <input type="button"> still renders with tons of extra padding you can't get rid of, even with padding: 0px; so buttons still show up super large in IE compared to all the other browsers.
Morphing Software
.. which is certain websites requiring IE to work.
What's changed in CSS specs for IE7 since August?
Has this been previously reported on slashdot?
What is your time limit on when infornation gets expired?
was Re:Old News
davecb5620@gmail.com
They still continue to work hard to implement the CSS2 spec which came out 8 and a half years ago.
I'm excited to see if they can implement CSS3 in time for my retirement in 30 years.
Keep your node to the grindstone kids, I know you'll get there!
Help me take back Slashdot. When did 'News for Nerds' become 'FUD and Conspiracy Theories for Extremist Nutjobs'?
"In addition, there is a long list of fixed bugs that plagued previous IE browsers for years"
It's be nice if Microsoft provided a list of every single unfixed bug in IE7 as well.
Where were you when the voynix came?
Hi all,
:hover events START BEFORE where the link is rendered and END BEFORE the rendered link ends.
IE7 isn't ready yet; it needs more testing!
For example, create a super basic html page. Within the <body> insert a single <p>aragraph, and within that paragraph, insert a(<a href="#">) link (</a>) - insert it somewhere after the start of the paragraph and before the end. E.g.
<body>
<p>This is a <a href="#foo">test link</a> for checking IE7 links</p>
</body>
Okay, view the page. It looks fine. Now Zoom 125%. The underscore below the link is rendered funny, and even better, if you move the mouse over the link, you'll find the mouse
*I believe* if the link has a background colour, then this background is rendered in the wrong place also.
Quite honestly I don't know how MS could've missed this... but there again....
Z.
FTA: We also extended our existing implementations to comply with W3C specifications:
Left arm starts tingling
Summation 2
Only listing shortcomings where support is present in all or nearly all of Firefox, Opera, Safari; the majority of its competition.
But it's still a huge improvement over IE 6 standards-wise, and I think Microsoft did a pretty good job taking their ancient IE 6 code and doing something decent out of it. IE 7 adds support for all CSS selectors, and even handles the + selector better than Firefox, applying styles correctly in dynamic updates.
Maybe with IE 8 they will be even more competitive with the browsers of today, standards-wise.
Beware: In C++, your friends can see your privates!
I'm surprised nobody has noticed this yet. If you load any page which contains frames, where the frames contain a large amount of HTML (or just text for that matter), the CPU will spike to 100% for some period of time that is related to the amount of HTML within the frame. I've tested this numerous times and it's a huge problem. IE6 does not show this issue at all. Go ahead, try it out. What's really interesting is while it's at 100% CPU usage, it will yield the CPU to other processes (if another process requires some CPU), but not to itself.
I hope they fix it, but something tells me they won't until I drum up some angry mobs.
FINALLY! Support for transparent PNGs so sites can finally look extra schmancy! I've been waiting for that forever. But too bad now position:fixed divs means evil ads that will follow you around on the page and cannot be closed.
Is it just me or is it not going to upgrade to Vista in here?
... Firefox 2.0 is available on Mozilla's FTP.
o x/releases/2.0/
(I'm using it right now).
http://releases.mozilla.org/pub/mozilla.org/firef
Y
It also looks like they fixed a problem in IE6 where a select/combo control in the background shows through a div with a greater z-index (i.e. the div should be in front and the combo hidden behind, but the combo was peaking through). I use javascript to change a div's CSS properties to make it into a "popup" by manipulating the position and display properties when certain events were triggered. It didn't work right in IE6 if there was a select element underneath, because the select always showed through. I read somewhere that the problem in IE6 was caused because the select controls were rendered as native windows controls and not rendered by the html engine. Anyway, it looks like they fixed it in version 7. I tried it out and it now seems to be working correctly.
How about the fact that you can't change ids on the fly? Or that referring to an object by ID returns one whose name is the ID you're looking for? These two bugs alone are responsible for the loss of two days of my life. Will Microsoft be giving those back to me with this release (which I can't install because I run a pirated copy of XP).
The flag just makes more sense than the constitution. - Judas Gutenberg
IE7 XSL Transformations are still the same. Writing an XSL stylesheet that transforms the same both in IE and Mozilla is a bit of a paradox. I've figured out ugly workarounds but am still in awe at the level of difficulty when trying to maintain cross-browser compatibility. One thing that I'm wondering about is how IE7 handles a malformed XML document. IE6 has no problem using a document that is not well-formed, whereas Mozilla will complain thoroughly. I guess we'll have to put that to the test.
Have you seen the new IE 7 acid 2 test results? http://www.webstandards.org/files/acid2/test.html# top They made it even better than the old IE. Now there is stuff that moves when you mouse over it and some random scrollbars too! Kudos to microsoft for creativity!
Isn't coincidence just amazing? Microsoft promotes a new browser with new features just as reports come out that IE is losing marketshare to firefox. For their next performance, do you think they'll pass the Acid2 test or do you think they'll join the committee that creates the Acid2 test so that they can pass the Acid2 browser rendering tests?
I hope they mean that PNG opacity support has been added as PNG transparency support would be almost completely useless (as we can already achieve this with gif).
How dare they adopt popular features like that? Who do they think they are, some sort of business?
New punctuation update "~" (no quotes) at the end of a line to indicate sarcasm. ~
Does anyone know whether IE7 finally supports the application/xhtml+xml MIME type? That would mean we can finally start serving XHTML pages the way they're supposed to get served, with no stupid browser detection. (I know, I know, IE6 will be around for the next six decades or so...)
IE7's CSS (and other standards) support hasn't changed since RC1. They've said this.
For a complete report on IE7's support, see WebDevout.com. For those thjo lazy (or embarrassed) to click the link, here's a summary of CSS 2.1 support:
In the grand scheme of things, what they did to improve IE7's CSS support is statistically insignificant. They basically took all the IE7 bug pages on the net and cherry picked what they felt like fixing.
Make no mistake: IE7 is little more than a marketing effort attempting to stave off the rise of other demonstrably better browsers. The few fixes they did put in are going to cause even more problems for developers who decide to support it (I'm not) because of how, which, and in what context the bugs are fixed.
Should we start preparing for a new generation of IE-only sites? Lord, I hope not.
Hand editing is another matter. Back in the old days, none of this nonsense was needed. You always got the best the browser had to offer. If you were neat and tidy about things, you'd add the <html>, <head>, <title>, and <body> markers. If you didn't feel pedantic, you just jumped right in. Starting off with "Hello this is my web page!" was just fine. Closing a <p> tag was unheard of, and even illegal in some web browsers.
It was about the same as writing an HTML formatted Slashdot comment: easy, simple, and fast.
Read the article How IE causes problems (28 pages). It was written for IE6, but updated for IE7. You can explore the both historic and outstanding problems in detail.
Until IE can handle the ACID smily face properly, (or FF for that matter) its still broken.
Call be stupid, but reading the HTML DTD, all the specs and very own long-time experience I can tell you that the !DOCTYPE tag at the beginning is REQUIRED.
for unadultered openness. What other site reserves screen space for the crytpo-sexual fantasies of its resident gimp.
Has it managed to be HTTP/1.0 compliant yet? For example, if I feed IE a .iso disk iamge file served with Content-Type: text/plain, will it render it as plain text in the browser window or offer to save it to disk? The correct response is to render it as text.
I'm sick of having to launch IE to download a special Linux boot CD because the person hosting it is too lazy to configure their server to serve it with the right Content-Type.
Oh, say does that Star-Spangled Banner entwine / The myrtle of Venus with Bacchus's vine?
Yay, I'm surfing and I'm not using up all of my memory. Joy.
I have been waiting to use :hover on arbitrary elements since I first got into web design with CSS. It's hard to appreciate for a person who has no or only very little CSS experience, but full support of :hover makes semi-advanced things easy. For example, a list item can be made to change backgrounds when it is hovered over. It's amazing how handy that is.
"it's not about aptitude, it's the way you're viewed" - Galinda
I tryied surfing through some demos at www.positioniseverything.net
s /IEt_fps.html
:-)))
:-) :-)
So, what can i say ? Many bugs realyl are not seen anymore, but...
They told they fixed most of them in that blog, for example they told they fixed the "italic fonts" bug... Did they ?
Italic bug consists of two parts:
1) with italic font, text becomes a bit wider, especially with letters like "g" in the beginning and letters like "t" at the end. IE 4=5=6, following its usual habit, expands the box to fit the font. IE7 does not expand the box, instead text is correcty written outside the box.
2) with non-italic font IE just does not renders text outside the box, it just crops it. Both IE 4-5-6 and IE7
http://positioniseverything.net/explorer/sidepage
It seems, those Indian guys been told "fix this!", then they looked at the title, said "a-ha! Italics..." and paid absolutely no attention to non-italic font.
I wonder, if IE7 just contains all those CSS/HTML well-known hack-arounds built inside its guts
PS: what is everyone silent about that 1st IE7 bug, so funny "found" by Secunia and so funny denied by Microsoft IE7 team ?
"She made a fuss, they made apologies, but everybody though the show was funny"
what about running IE7 with WINE on linux? if you get that working, thier is probably already those who got cygwin running X, and WINE on 2000/98.
I've tried this hack in the past, but IE has too many bugs for it to be useful. For example, if you do this to use a PNG file as a background image, links and forms in front of the image stop working.
He who lights his taper at mine, receives light without darkening me.
tested ie7 again. it still fails to format a page the way firefox, opera, or safari do. has no clue about centering. has no clue about lots of stuff. it *is* better than ie6. big deal ...
REPORT ALL OBSCENE MESSAGES TO YOUR POTSMASTER
If the system universally rejects malformed documents, that is acceptable, IMO. However, if it doesn't, then how it handles them is very relevant as one must be concerned about malicious XML being used to perform a buffer overflow attack, for example.
(I came across this post while meta-moderating, in case you're wondering...)
Ben Hocking
Need a professional organizer?