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.
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?
Whose fault was it for using a partially-supported standard? Did somebody at MS hold a gun to your hand and demand that you use PNG?
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!
Did somebody at MS hold a gun to your hand and demand that you use PNG?
Now listen, shee... you're gonna use PNG... and you're gonna like it! Or my six-shooter may have to loose some lead on you, shee? Nyah...
GetOuttaMySpace - The Anti-Social Network
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.
... 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
The Alpha filters still work... With the exception that any text rendered over an Alpha filter (e.g. a .png or an Alpha transparency) looks like ragged shit, as for some reason it is not rendered anti-aliased. For .pngs you can remove the Alpha png filter nonsense, but so far I have no solution for text on top of an alpha transparency.
Why am I not surprised that in fixing IE they have broken the previous, non-standard hack crap?
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
We have a design spec that we're meant to follow, either we do it in flash or we do it in HTML, CSS with a bit of Javascript and some alpha transparency PNG's.
Which site would you rather go to?
I know which i'd prefer.
I was faced with that exact conundrum a couple of years ago, either I can learn Flash and create a site that is unusable in text browsers, unusable to blind users, unusable to non windows and mac os users and an inability to copy text from the website etc. Or code it in HTML, CSS & Javascript (with a few alpha PNG's) which I already knew. Which the MAJORITY of web devs know.
I created it in HTML, CSS and JavaScript.
That said the site which is still up works fine in IE 7 as well as 6, no need to tweak the JS for the alpha png stuff.
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!
Well, you see, when you fix a bug, you, well, fix the bug. All the CSS hacks out there exploit unfixed bugs, so you see by fixing them, they ruin your hacks. That's why you don't hack. Use conditional comments.
"The need to build the internet comes from something inside us, something programmed... something we can't resist."
Have you been hiding under a moonrock? :-D IE6 supports PNGs binary transparency, IE7 finaly supports alpha channel as well.
Analogies don't equal equalities, they are merely somewhat analogous.
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 have asked google first :(
http://www.tatanka.com.br/ies4linux/news/28