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 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
Why would they when other people are already doing that
"The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
FTA: We also extended our existing implementations to comply with W3C specifications:
Left arm starts tingling
Summation 2
Installed IE7, found two problems within 10 minutes.
Does not work with SalesForce. Buttons do not render. They'll appear as a thin line without text.
IE7 does not work with our SharePoint / WSS v3 Beta (with R2 patch applied). Excel views crash. Works fine with IE6 and Firefox.
IE7, IMHO, is not ready for prime time. Even uninstalling is somewhat hidden. Hint: Control Panel, Add/Remove software, show Windows Updates, then find IE7, remove.
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.
... 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
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
No the zoom feature is new to IE7. They did (and still do) have the ability to change the text size.
Firefox by contrast doesn't have zoom at all. But Opera's zoom is quite considerably better than IE7's!
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.
SP2 breaks lots of stuff. Besides, on my PC at work I don't go around installing system upgrades... If anything breaks it's my fault for not asking the appropriate department to do it.
Global warming is a cube.
It involves starting the setup procedure, and then replacing the hacked inf with the original before the cryptographic service (yes, it has to be in manual or automatic) can verify it. This is easier to do with a slow computer, of course (you may need to write a batch file if you run a modern processor). At least, this works to install WMP11 under Server 2003. What'll happen with IE7 under W2K is very much a mystery, though I'd be surprised if your explorer shell still worked after completing setup.
I'd try this in a VM first, if I were you.
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.
No, it doesn't.
Too late ^^ However, your trick has worked. IE7 has installed itself on the system, asked me to reboot;
I did it, but then things started to go wrong.
It had a problem with IEDKCS32.DLL during the post reboot install. Now, explorer.exe crashes in shlwapi.dll, and more mysteriously, when I run iexplore.exe, a message box appears and tell me that iexplore.exe is not a valid win32 application...
So I sum up: no more IE (don't care, use seamonkey), but no more desktop also (for now?)... which is more embarassing!
should have asked google first :(
http://www.tatanka.com.br/ies4linux/news/28
SP2 breaks nothing. Already broken systems (malware typically) fail under SP2 because of the aforementioned breaks not being compatible with new fixes in SP2.
I used to get high on life, but I developed a tolerance. Now I need something stronger.
So I heard, and it kept me from installing it for a good few weeks until I was reasonably confident I knew what the potential dangers were. In practice, when I did install it, it caused me absolutely no problems at all.
There were a handful of major applications that did have problem reports linked to SP2 for a while. However, the developers were generally quick to fix these, and I haven't heard of an SP2-related problem report for any legitimate software other than system tools for a very long time now.
If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.