Discussion on:
View:
Show:
I have ie7 rc1 but could not locate the developer toolbar mentioned. Where is it really?
Something we could all use to get over the bugs in IE7
While we cannot ignore the RC1 of IE7, it represents no change for a lot of web authors.
We'll just stick to creating sites that conform to Standards and hope that, some day, IE will catch up.
We'll just stick to creating sites that conform to Standards and hope that, some day, IE will catch up.
How, the fact that you had to write non compliant code to make IE work (and still do !) or the fact the IE was happy with non compliant code.
The only 'fault' was using IE as the standard in the first place, everything after was a consequence of that mistake. Which goes on and on and on and on, because of us, obviously !
The only 'fault' was using IE as the standard in the first place, everything after was a consequence of that mistake. Which goes on and on and on and on, because of us, obviously !
What a cop-out! It's just easier to "pass-the-buck" and blame someone else when it is easy to! Good on you Microsoft (note sarcasm)... for being so lazy that is and not delivering on "STANDARDS". It is really just another easy way to maintain their apparent monopoly if you consult me on the issue.
Use shared borders
No use layers
No use frames.
Meanwhile us poor ***** have to write pages that use all three. Surprisingly they are three times bigger than they need to be, don't always work, cost more to test, maintain and enhance.
Besides you should use CSS anyway, it will render the same on each browser because it is a standard.
ROTFCMAO
C = Crying
No use layers
No use frames.
Meanwhile us poor ***** have to write pages that use all three. Surprisingly they are three times bigger than they need to be, don't always work, cost more to test, maintain and enhance.
Besides you should use CSS anyway, it will render the same on each browser because it is a standard.
ROTFCMAO
C = Crying
Mozilla Firefox has an even more comprehensive web development tool namely the Web Development Toolbar. And with the IE tab extention you can effortlessly test your web pages in both browsers to ensure that they look ok in both of them. You won't se IE7 include a Firefox tab to test your web pages in Firefox.
I'm really sick of IE messing up all my hard CSS coding work each time I work on my web sites in Firefox. After long hours of coding I get my pages just like I want them to be in Firefox. When I view them in IE I discover several CSS bugs that puts everything in places where they shouldn't be, just because of Microsoft's ignorance to supply better and valid support for CSS in their browser.
If every user of IE knows what we as web developers have to go through to deliver our pages in their favourite useless browser, they will be more likely to make the switch to Firefox and spare us hours of time, time that can be spent to make our sites even better. (OK maybe that will only happen in a perfect world)
http://www.cybertopcops.com
I'm really sick of IE messing up all my hard CSS coding work each time I work on my web sites in Firefox. After long hours of coding I get my pages just like I want them to be in Firefox. When I view them in IE I discover several CSS bugs that puts everything in places where they shouldn't be, just because of Microsoft's ignorance to supply better and valid support for CSS in their browser.
If every user of IE knows what we as web developers have to go through to deliver our pages in their favourite useless browser, they will be more likely to make the switch to Firefox and spare us hours of time, time that can be spent to make our sites even better. (OK maybe that will only happen in a perfect world)
http://www.cybertopcops.com
Lets see according to W3, the only browser out there that is 100% compliant is Opera and we all know what a huge percentage of the market they have. The problems that are still occuring go back to way before IE even existed and started with Mosaic. Every body likes to point the finger at MS and say it is their fault, but they tried to have standards set that would be rendered by the browser, but developers and everyone else kept on saying we can do better, therefore we have our current mess. And for developers who code for Firefox, you are only repeating mistakes of the past because though Firefox may be able to pass Acid2, that is only some self interested parties idea of what the standard should do and not W3 standards either.
The proper rendering of web pages won't happen until a new rendering engine is created that makes it clear and concise how a page will appear and all browser manufacturers start using the new engine. At this point in time neither mosaic or Geicko are up to the challenge. At least MS realises that there are many web pages developed by companies that still rely on older standards and caters to them. There are just as many intranets out there as there are on the Internet and their needs have to be acknowledged.
The proper rendering of web pages won't happen until a new rendering engine is created that makes it clear and concise how a page will appear and all browser manufacturers start using the new engine. At this point in time neither mosaic or Geicko are up to the challenge. At least MS realises that there are many web pages developed by companies that still rely on older standards and caters to them. There are just as many intranets out there as there are on the Internet and their needs have to be acknowledged.
older proprietry extensions are. That and XHTML never got widespread use.
I wouldn't say IE was the problem, everybody was coming out with extras. The real problem is they all wanted their proprietry stuff to be the standard. None of them were going to agree to that, so we are where we are now, a mess. Trying to lay blame now is a waste of time, I'll applaud efforts to work to W3C which is the standard and decry any departure from it. IE get's pointed at because of it's popularity, for obvious reasons most sites are designed with IE so all the non compliance looks like their fault. a penalty for being successful I'm afraid.
I remeber frames and layers and shared borders and events bubbling up and events bubbling down and this and that and those. It's why I try to stay out of web development, it's total pain in the ass.
I wouldn't say IE was the problem, everybody was coming out with extras. The real problem is they all wanted their proprietry stuff to be the standard. None of them were going to agree to that, so we are where we are now, a mess. Trying to lay blame now is a waste of time, I'll applaud efforts to work to W3C which is the standard and decry any departure from it. IE get's pointed at because of it's popularity, for obvious reasons most sites are designed with IE so all the non compliance looks like their fault. a penalty for being successful I'm afraid.
I remeber frames and layers and shared borders and events bubbling up and events bubbling down and this and that and those. It's why I try to stay out of web development, it's total pain in the ass.
Web development has been a headache since day one.
HTML tags, Cookies, Javascript, ActiveX controls, Java..., all disgusting.
HTML tags, Cookies, Javascript, ActiveX controls, Java..., all disgusting.
>There are just as many intranets out there as >there are on the Internet and their needs have >to be acknowledged.
Quite correct, but an intranet can be designed for a single flavour of a single browser as many are. When you get into the ethernet it would be nice to have at least some conformity between the various browser engines - trying to code for all possible varients of IE is a task that a lot of us no longer entertain (some code from v5 onwards, some only for the last and current iteration), let alone the versions of IE that ran on Macs. Whilst I appreciate your point about the heritage of IE (Mosaic) I still have to say that it is inevitable that at some point Microsoft will have to abandon legacy support. Without doing so their coding problems for the future (further development of IE and the O/S) are just going to get more and more convoluted and the time/man hours unjustifiable.
P.s. As an aside, the ACID tests are developed by the W3 who, most definitely, are vested interest parties to the future of web development.
Quite correct, but an intranet can be designed for a single flavour of a single browser as many are. When you get into the ethernet it would be nice to have at least some conformity between the various browser engines - trying to code for all possible varients of IE is a task that a lot of us no longer entertain (some code from v5 onwards, some only for the last and current iteration), let alone the versions of IE that ran on Macs. Whilst I appreciate your point about the heritage of IE (Mosaic) I still have to say that it is inevitable that at some point Microsoft will have to abandon legacy support. Without doing so their coding problems for the future (further development of IE and the O/S) are just going to get more and more convoluted and the time/man hours unjustifiable.
P.s. As an aside, the ACID tests are developed by the W3 who, most definitely, are vested interest parties to the future of web development.
I wouldn't count the Developer Tool Bar as a new feature of IE7. I've been using the DevToolBar since the first of the year with IE6. It has come in handy. As for IE and compliance with the standards, with over 90% of the visitors to the sites I develop being IE users Microsoft is the defacto standard for my development. While I do check that my sites look and work as expected in FireFox and Safri, and I'd much rather use the W3C standards, I have to develop for the majority or my clients will go to someone else to get their sites designed and programmed.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
