Linked by Matt Brewer on Fri 12th Dec 2003 20:43 UTC
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
More News »
Sponsored Links



>>>To stay on-topic, it's not that IE is a bad browser, but just that other browsers offer more functionality and are standards-compliant. The biggest effort is to educate web site providers - especially government ones - to make sure that their content is accessible by all modern browsers, not just IE.
The biggest problem is the FrontPage is really an Internet Explorer production application (now SharePoint production app as well), and not a HTML design app.
Mine you that in FrontPage 2003, you can TURN OFF all the Microsoft specific codes. But the problem is that half of the features in the menu are greyed out.
The best way to create a webpage is to write and group the contents semantically --- with zero formatting. Then you apply the layout with css. Then you apply the skin with another css file.
http://www.alistapart.com/articles/slashdot/
http://www.alistapart.com/d/slashdot/indexwithoutcss.html
http://www.alistapart.com/d/slashdot/indexwithoutmarkup.html
http://www.alistapart.com/d/slashdot/index.html