W3C On How To Fix Browsers 343
kellan1 writes: "The W3C has published a note Common User Agent Problems, aka why do web browsers suck, and what can you do about it?"
This discussion has been archived.
No new comments can be posted.
W3C On How to Fix Browsers
Related Links Top of the: day, week, month.
Saliva causes cancer, but only if swallowed in small amounts over a long period of time. -- George Carlin
HTTP auth (Score:2)
Oh, another thing that pisses me off about IE on the Mac (probably most other browsers as well, but I'm running into this now on Mac IE5.0) -- why the hell can't I use the standard editing conventions for my platform in a TEXTAREA? There's no way to move a word or paragraph at a time (like option or command arrow...)
Oh well....
Re:hmmm (Score:2)
What do you think point 3.2 [w3.org] is referring to? As far as I know, IE is the only browser that departs from the HTTP standard by ignoring text/plain as a content type. I don't consider a browser that thinks "Sure, the server says it's text/plain, but I know better" to have "comprehensive support for W3C standards".
Re:Mozilla (Score:3)
Just a quick correction: Use TEXTAREA, but add an option to it, eg. <TEXTAREA FORMAT=HTML>. That way old browsers still support it, only the formatting is missing. Also the format would be extensible.
Re:Konqueror (Score:2)
One thing that I really like about Konqueror is that you can set the browser ID tags. Most of the time I leave them set to "None of your fucking business (Mozilla 5.0 compatable)" but if a site that I actually want to see gives me trouble I can switch over to being IE 5.5 pretty easily.
_____________
Re:Mozilla (Score:2)
Actually, XEmacs has an API by which X apps can embed XEmacs as a text editor. That would be fine with me, I'm a Emacs whore...
However, I do NOT want to run an Emacs key-binding tutorial with each client of mine. "No, see, to make the text bold, you have to have the hm--html elisp package, load it in your .emacs file, and the key binding is [ctrl-x, ctrl-w, b]" I don't have that kind of patience...
I'm talking simple, simple stuff. Bold, italic, headlines. Keep the TEXTAREA, add a new one <FORMATTEXT> , or something similar. You get a textarea-like window, but when you type it shows the text in the font that the stylesheet gives it, you can bold or italicize text, etc.
Actually, something a lot like AOLpress would be nice...
Re:Whee..Just embed Frontpage! (Score:2)
So how much did that cost you on eBay?
Re:Good luck to them (Score:2)
I need the <TEXTAREA> for many things, such as posting application forms, stuff that sends e-mails---most of the stuff is not in HTML. If you restricted it to HTML rendering then you've removed the flexibility of the widget.
when there is a web browser that is isn't brainsick...
It's not the fault of the browsers that they were implemented to specification. If they did in fact implement HTML rendering in the TEXTAREA widget or even if they added a HTMLAREA widget in a certain brwoser it would only cause webmasters more grief since it would be another thing which "Works in IE, doesn't in Netscape" or vice versa. If anything, blame the W3C for not coming up something that people need.
Re:Don't hide 404 messages! (Score:4)
In that case, the proper status code would probably be 410 Gone [w3.org]
netscape! (Score:4)
we take great joy in yelling a different fix for their broswer every day out our window;
"how about rendering tables correctly?!"
"how about filed widths being consistent?!"
id be happy to yell any fixes anyone would like to see implemented.
oh the headaches of netscape. keeps me with a job though.
Re:hmmm (Score:2)
But now I'm confused. IE is better than most browsers as displaying broken HTML -- why is he mad at MS?
Re:How about following the DTDs? (Score:2)
"Browsers started going to hell in a handbasket when they forgot why HTML was around in the first place - to make a platform-independent system for sharing information. Thus, a web page in Netscape *should* look different than a web page in IE, *however* the content should be the same. "
Coming from somebody who's complaining about the fact that webpages don't look the same on all browsers, because they don't adhere to the standards.
News flash. Content is not the most important part of a website. There goes the karma. But hear me out. Content is one of two things that are equally important, and if either are lax your website is useless. The other is user experience. You may have the most content-rich site in the world, but it doesn't matter if it looks like shit. And you can have the nicest looking site in the world, and it won't matter if it's got a fucked up interface or you have no content. Just look at some of the more abstract graphic artists' homepages out there.... They look great, but when you can't tell where to click or what clicking there's gonna do, you head straight for that little x in the corner.
When will you people learn, that the look and feel of a site Is just as important as it's content?
Frankly, I love explorer, and they do a lot more complying (is that a word?) to standards than netscape, and a whole truckload more than they have to.... W3C can jump up and down, but as it stands, IE is the standard, and it ain't gonna change for a while, because users are happy and that's what counts the most.
</rant>
--Gfunk
What's wrong with browsers.. (Score:2)
Re:I think W3C missed one... (Score:2)
Re:Logout (was Re:for you browser writers out ther (Score:2)
Thanks for the tip, though.
All your dangifiknow [dangifiknow.com] are belong to us.
Re:hmmm (Score:2)
Down that path lies madness. On the other hand, the road to hell is paved with melting snowballs.
Re:I dont understand why a browser hasnt done this (Score:2)
I highly recommend turning on the option for having one file operation window. It will even tell you your total download rate if you're downloading multiple files.
Another neat GetRight-ish feature (but better) is the little menu that comes up when you select a URL that isn't a link. Klipper, the ultra-neat clipboard tool asks if you want to open it in Konqueror, or (depending on availability) Nestcape or Mozilla, or it will let you pop up a window to edit your selection and then allow you to choose again. You can add more applications and regexes for processing. By default, mailto: links can be handled by kmail or mutt.
There are some features that are lacking, however. I can't click on a partial file (Konqueror adds a
DAV:// should work for "Web Folders" (Score:2)
--Mike--
Re:hmmm (Score:2)
vs.
I'm impressed that Mozilla has come so far in it's ability to render HTML, but that's only a small subset of the W3C stuff.
Re:How about following the DTDs? (Score:4)
--
Re:How about following the DTDs? (Score:2)
;)
Re:hmmm (Score:2)
Er, that was me, not Alan.
And I do regret it -- if I could edit the original, I'd change "most comprehensive of any browser" to "...very comprehensive support...".
Do you speak Canadian? (Score:2)
Since when is Canadian a language?
--
Re:The browser wars at at fault. (Score:2)
s/stagnated/suffocated/. The reason NS was stuck at version 4.x for so many years is because MS "cut off their air supply". They couldn't afford to develop a new version because there was no longer any way to recoup the development costs.
That is why we have the situation we have today. A lot of people liked (and still like) Netscape but were stuck with the 4.x browser because of MS's illegal business practices. So a lot of web developers had to develop for a bitrotten browser instead of making use of new standards like CSS (yes, NS4 had some sucky CSS support (so did IE 4)). Finally, everyone said "fuck it" and developed for IE 5.
If the browser war hadn't been "won", I'm sure we would have seen a lot more innovation from both NS and MS over the past few years. NS and MS would still be creating their cute little tags to one-up each other, and W3C, following their leads, would design an elegant solution to do the same things (and then some) The Right Way. I suspect we would've seen much more interesting developments from that competition than the relatively trivial things we have seen without it.
Since the end of the browser war, what sort of developments have we seen? IMHO, the most significant developments in the web browser have been: HTML (duh :), client-side scripting (Javascript), integrated VM (Java applets), and style sheets (W3C CSS). How many of those happened after the browser war ended? Have we seen anything of comparable signifigance since? I mean, "hover"? Give me a break! CSS came about just as the browser war was ending, and that is where the real innovation stopped. I don't think that is a coincidence.
When MS won the browser war, it wasn't just NS who lost. We all did.
Re:The browser wars at at fault. (Score:2)
IE supports the hover: property for links. Mozilla is attempting to support it for everything. That's just a teensy weensy bit harder. We'll get there, though.
In addition, a Mozilla developer says "From reading the CSS WG mailing list, it looks like the exact definition of hierarchical hover is still being hammered out. I'm not sure we should put an implementation of it into our code until we are sure that we know how exactly this feature should work."
It's Bug 5693 [mozilla.org].
Gerv
Re:netscape! (Score:2)
This is part of the reason that web browsers suck: because people demand that they render broken content "nicely".
Missing </td> and </tr> tags aren't broken, yet Netscape can't render the page. According to the specs, end tags aren't needed on table elements or list elements; it can easily be deduced that if you have a <tr> tag, the previous table row and any of its open columns have ended. If Netscape simply followed the specs I think we'd all be happier.
But the bigger problem is broken HTML. While it may be the author's problem, your browser should render it as best it can. One reason is simply that today's HTML may be considered broken in a few years, and vice versa. At any rate, it's the right thing to do. If IE was the browser that didn't render broken HTML, we'd see all kinds of comments about how stupid that is.
Michael
Slashdot's text area (Score:3)
Re:hmmm (Score:3)
Re:What I find completely amazing... (Score:2)
Some people write pages that stick to the HTML standards, though for the most part they are simpler in design because that's the easiest way to stick to the standard. But quite frankly, it's also usually (not always) less interesting.
The browsers will still render the same page differently because that's what the standard allowed them to do - it didn't dictate the exact appearance and left it to the browser implementors.
Besides, they create the Amaya browser, which is supposed to render correctly, and you will see it looks pretty different from everyone else's browser. Maybe we should all just use Amaya?
Re:for you browser writers out there (Score:2)
Re:What I find completely amazing... (Score:3)
There is no definition of how tags are supposed to be rendered. That is explicitly left open by the HTML standard, and for good reason. CSS specifies more of that, but it's still not complete, and again, there are good reasons not to fully specify the rendering.
It is simply not true that the rest of the work is "a piece of cake", not when you're dealing with something as complex as the W3C standard definitions and all their interactions. If you don't believe it, try writing a browser yourself.
But the biggest problem is that despite the fact that HTML 3.2 and 4.0 are specified, it doesn't matter because Web page authors DO NOT stick to the standards. They write buggy pages which more or less render OK in the browser they happen to be using, and then they're done. There are almost no pages which adhere strictly to the W3C definitions, and that's why results vary from one browser to the next.
Re:netscape! (Score:2)
When I'm browsing content on my own web site, I want malformed content to stink up the place, so I can call the person responsible and have them fix it.
When I'm looking up emergency directions for performing CPR, I want the content even if the designer screwed up.
Re:Good luck to them (Score:2)
The browser you want has been out since 1996. I am using it right now. There's just one little catch, though: you need an Amiga.
Whenever AWeb [amitrix.com] does a textarea widget, it has a little button in the lower right corner. If I click it, then the text is immediately loaded into the greatest and easiest-to-use text editor in the world. Whenever I tell the editor to write, the textarea gadget is immediately updated.
What is the greatest text editor in the world? It's whatever you want it to be, set in the browser's preferences.
---
I think W3C missed one... (Score:3)
Re:Slashdot gets it wrong again (Score:2)
w3c's guidlines (Score:4)
The W3C does have a tool you can use to see if web pages are compliant with their html specifications. Which, of course, almost no one's are.
As far as I am concerned, if this guy's [helsinki.fi] web page is not html compliant, I am not going to worry if mine isn't.
Content-encoding (Score:2)
Content-Encoding: gzip
If saved locally, the filename on most computers should be html40.ps.gz for the applications to recognize the file type.
Wrong: Saving this compressed PostScript document as html40.ps is likely to confuse other applications.
Surely the correct thing to do is to save the _uncompressed_ file as html40.ps? Aren't most html files sent over the web sent with gzip content-encoding?
Re: ...wrong again. (grow up) (Score:2)
Bring back the "Find" button (Score:2)
Netscape*toolBar.numUserCommands: 1
Netscape*toolBar.userCommand1.commandName: findInObject
Netscape*toolBar.userCommand1.labelString: Find
Netscape*toolBar.userCommand1.commandIcon: Find
I find it useful, at least...
Ultimate Test HTML (Score:2)
hmmm (Score:4)
the behaviors described are not protocols officially accepted by MS. (just look at the behavior of the browsers)
Given the dominance of MS in the market, is this document even relevant? [even though it is brilliant, insightful, and written by people who care about what is going on]
I am just glad we haven't progressed to the point where Microsoft "red" is a shade between black and blue.
Allowing users to select transfer encoding (Score:2)
The user agent should allow the user to set the transfer encoding in the HTTP requests sent out.
I don't understand why this pref is necessary. Browser makers generally have a much better idea of what the best transfer-encoding types are than users, and most users wouldn't have any reason to change this setting.
The real reason browers suck (Score:2)
It really is Microsoft's fault.
Why? Because prior to the explosion of browsers and the web there was no good, ubiquitous technology that allowed platform independent distributed computing. There were plenty of technologies at the time, but you wouldn't find any of them on Windows machines. Rembember Bill's pre-Netscape attitude about the Internet? "Oh, it's just for hobbyists, the REAL *information superhighway* is going to be MSN!" Hence Windows had none of the built-in network-ready functionality that would help form a base for *real* distributed computing in a way that would actually work.
Once browsers became widely available for Windows (i.e. Netscape) the web began its explosion because it enabled what everyone really wanted in the first place, but Windows wouldn't give it to them, platform-independent networking. Unfortunately, since the browser represented the only real choice to accomplish this, it started being used for EVERYTHING. Not just hypertext document traversal and simple form submission for which the web was designed, but full-blown remote applications for everything you could imagine. Hence the browser wars reached a feaver pitch because now everything under the sun had to be supported, but it was on top of a model (batch-style client fetch) that just wouldn't support it.
And we're still paying the price today. My own job is in the development of a complicated user interface used to configure a complex system. Pretty much hell to do in a browser, but we break more than half of the W3C's rules because we need it to act like a real UI, and the decision to go browser-based stems ultimately from the fact that there really aren't many better alternatives (well, Java maybe, but it has it's own problems, --I won't get started on how Microsoft screwed that up, too). And now, God forbid, we're faced with more Microsoft "vision" in .NET.
If Microsoft had the slightest CLUE about networking, the world would be a different place today. Hell, we probably wouldn't even be facing a possible recession, and the dot-com implosion most likely would have been much less severe if everyone had real tools and applications that interacted on the Internet in a sensible way.
Sorry if this is just more /. sour-grape Microsoft bashing, but if anyone can't point out why I'm wrong, I'd love to hear it.
Re:Good luck to them (Score:3)
---
A good solution (Score:3)
2. Have the web browser try to compensate as well as possible for mistakes, as long as doing so doesn't interfere with #1, above.
I.e. follow the Internet maxim, "be conservative in what you do, and liberal in what you accept"
3. Issue a web page quality feedback to the user so if a site has bad HTML, the user knows, so she can fix the site if it is hers, let the web master know if someone else is responsible for the site, know that a company can't do web pages right (great if you are browsing a web page design company's site!
A good implementation would be, for example, an icon which shows quality, and when clicked shows any errors in the page. E.g. if the page is good there would be a smiley face and a tool tip would say "No errors - high quality page", and if the page was bad there would be a frown face and when you clicked it you'd get a window opening with a list of the errors in it. A really good implemenation would have a whole site of icons for perfect, good, ok, bad, and horrid HTML. Of course, the lower the quality, the more likely there are to be problems rendering the page...
How about following the DTDs? (Score:5)
The DTD merely says that this text is in a paragraph. Unfortunately, most browsers have embraced and extended this to assume that all browsers have the exact same layout. Thus, changing font sizes or types in your browser makes the page look just plain wrong.
Back when the DTD was being followed, *everyone* built web browsers, and all was good with the world. The content was similar, and no matter what the platform, you could still browse. Then came . And . And and all hell broke loose.
Now we're in an IE world. One browser for everyone. Netscape is flailing, Mozilla is close, but MS has free run of the DTD.
If you really want browser wars to heat up, you have to make usre that the browser followed the DTD properly so the display is not driven by the content, but is driven by the end user, as it should be.
Re:What I find completely amazing... (Score:3)
There are many reasons why two correctly-functioning browsers will display the same page differently. The <p> tag, for example, without style information, just means "paragraph" - there's no reason different browsers might not have (compiled-in or user configured) different default fonts, default spacing between paragraphs, default paragraph indentation, etcetera. Even with style information, the user can override the author's preferences.
Web pages are not Postscript or PDF documents. HTML authors who try to make pages that look exactly the same in all browsers Just Don't Get It.
Tom Swiss | the infamous tms | http://www.infamous.net/
Good luck to them (Score:3)
Here I am, typing into a <TEXTAREA> , a widget so abhominably broken, it only understands the barest rudiments of text editing (hit key, print letter), and they're worried about broken or missing <A> tags.
Come on, people... one of the most common uses of the web these days is to post messages on a weblog-type site (like, oh, Slashdot) -- and there isn't a widget that we can use other than the <TEXTAREA> so normal people can type text in, highlight a few words, and hit a BOLD button? They have to learn to use <B> tags? What is this, 1983?
I'll tell you what -- when there is a web browser that is isn't brainsick, then I'll care about the UI implementation of broken <A> tags...
XHTML to the rescue!!! (Score:2)
Hello XHML (HTML described in XML)
As other posters have noted, a lot of problems have been caused by the so called "race to the bottom" where current browsers try to render the worst HTML code possible.
That is exactly why we need XHTML where the authors are forced to write DTD compliant documents to start off with or they simply will not be displayed.
This means that the people writing XML processors for a given browser don't have to worry about supporting anything outside the specification. (Although displaying useful error messages for incorrect documents may be a sticky point)
For a good description on why we need XHTML, see http://www.webreference.com/xml/column6/ [webreference.com]
Re:Bring back verbose loading! (Score:2)
--
Re:Speaking of buggy browsers... (Score:2)
---
Re:Content-encoding (Score:2)
This is nonsense (Score:2)
Though I'm sure Jakob Nielson is delighted.
Bring back verbose loading! (Score:4)
I remember old browsers used to display information like:
The trend I've seen in modern browsers simply say "Loading" or "Opening" without telling me what's happening. Having the extra information would help when troubleshooting what section of the content isn't loading.
Re:w3c's guidlines (Score:5)
A little less hero worship, I think, would serve well.
Useability (Score:2)
"Oh so and so browser doesn't render properly"
"Well, your browser introduced proprietary crap"
"At least my company isn't co-opting the world"
Blah, blah, blah. While I agree with many of the posts that lament about rendering and a lack of standards - I think we all need to get back to the basics: Useability. We've become so enamoured by our ability to 'do things', we've forgotten that the majority of people surfing beside us have little or no computer knowledge. They don't see the difference between a static HTML page and a page that was built on the fly using PHP and mySQL. What they do notice is incoherent navigation schemes and huge download times.
Having worked extensively training new computer users of all ages, I think I have more hands-on useability experience than your typical Slashdot reader. The following are some improvements that need to be made (by browser authors and web designers):
- 404 Errors, 500 Errors and so on. As one poster mentioned already: provide more information about these errors. A 404 File Not Found error means absolutely nothing to an 85 year old man. Make your own set of error pages that explain the error and how it could be fixed. Also provide a listing of other resources that are available on your site.
- Information Architecture: Make the information on your page easy to find. Don't bury your content underneath a pile of Flash animations. Sit down and plan a navigation scheme that will allow users to easily find information on your site. Any first time computer user should be able to find the most obscure piece of information on your site in under a minute.
- Another poster brought up another great point about . This is a terrible way for people to enter information. A first time comptuer user has no concept of HTML tags, as simple as they may be. We need to develop something that will allow them to highlight text and make formatting changes like they would in a word processor.
- Cluttered Browsers: Most of the browsers available today are cluttered with buttons and advertising. Keep It Simple Stupid. People become easily confused by a wide variety of buttons. ICQ is a decent example. You have Basic and Advanced Modes. Web broswers should be the same. A basic mode has your most rudimentary buttons (forward, back, stop, bookmarks) while your advanced mode allows access to the "Search" and "History" 'tools' ahem.
- Documentation: Provide some damn documentation with your browers. The current documentation is terrible. People can't find solutions to their problems... Mainly because the current documentation is poorly written and the information architecture of the documentation is terrible too. Make it simple. Have a list of "How-To" guides that explain basic concepts and provide screenshots.
They may sound like inane suggestions, but they're improvements that would go a long way in making the surfing experience of beginners a lot more enjoyable.
for you browser writers out there (Score:5)
I don't think I'm the only one that finds it quite annoying to have to exit and restart my browser in order to make it forget my HTTP authemtication information. I believe Netscape and IE both have this problem.
All your dangifiknow [dangifiknow.com] are belong to us.
Since when is W3C a standardisation organisation? (Score:2)
And there are a lot of these small things. An organisation that calls itself an official standardisation organisation should first think if they're capable of doing the job correctly before stepping forward with all kinds of 'do this and do that and everything will be allright'.
Until then, I don't see HTML as a 'standard' which is standarized by a standardisation organisation, but 'just a propriatry language'.
--
Other useful changes (Score:3)
Re:How about following the DTDs? (Score:2)
G-funk wrote,
This is just wrong.
If look and feel is just as important to you, the provider of the information, then the WWW with HTML is not for you. You want a flash presentation or a PDF.
HTML is rendered on multiple platforms, on different media, for people with different requirements. There is simply no way one can ensure that the look and feel of a site is preserved. None. Not only that, but the attempts by authors to make them so generally result in making the content itself inaccessible to between 5% and 20% of readers. This is obviously screwy.
I'm sure there are some applications for which the exact presentation of content is a crucial component of the content itself. I can't recall the last time I came across such a web page though. While there are thousands (millions?) which do sacrifice accessibility and usability on the altar of `user experience'.
If you need exact presentation, use flash and PDF. If you actually have anything important to say, use HTML and live with the fact that it won't look (or sound, or print) the same to every reader. Just cope.
Simpler browsers (Score:3)
-thinmac
Re:How about following the DTDs? (Score:3)
Baloney. This is the information age, not the presentation age. I never go to a site to see what it looks like today. I want to find out what information is there today. If I'm interested in a 'user experience' I'll watch the commercials during the Super Bowl.
If the presentation is poorly done (the definition of 'poorly done' is different for different people) then it might be useless to some people. If there is no or low quality content then the site is useless to everyone, except perhaps to those who visit sites just to see what they look like.
Consider how cleverly crafted presentation will be lost on someone who is blind, color blind, epileptic, deaf, accessing the sight from a mobile phone, or some low bandwidth connection, etc.
Most people don't go to the internet just to look at the pretty pictures.
--
Re:Browser size (Score:2)
Agreed. The concept of user interface design did not begin at Xerox PARC in the 70s. It goes back to stuff like stone tools and papyrus manuscripts.
Ever wonder why magazines and newspapers break text up into columns rather than letting a paragraph run the entire width of the page? Hint: it's not because of adverts, or because their machines couldn't handle it. It's because they realized that eyes can't handle that much text all at once.
BTW, median screen resolution is 800x600, and it's likely to get smaller in the next few years. Think Palm.
Re:Content-encoding (Score:2)
This section bugged me too. IMO, the real mistake in that example is theirs by choosing an inaccurate file name. If it's a gzip archive of a postscript file, it should be named html40.ps.gz on their end, not html40.ps.
BTW, most HTML files are sent without the content encoding command. Here's some example HTTP headers passed when I hit the Preview button:
Re:A good solution (Score:2)
The biggest user agent problem I see is resultant from plugins. (and *cking Java applets) Most plugins only work with IE, and then after you download and install them to view the page, you are forced to reboot, then come back and re-find the page. And for all of that, you get a 3d rendered penguin in Metastream.
And Java applets... Talk about "Is my computer locked up??" kinda days.... Egad...
Re:netscape! (Score:5)
This is part of the reason that web browsers suck: because people demand that they render broken content "nicely". I would much rather they render correct content properly, than do a half-assed job of rendering everything. "Best guessing" is precisely what leads to the non-deterministic behaviour the original poster complained of.
If malformed content doesn't show up correctly, it's the author's fault, not the browser's.
Re:hmmm (Score:2)
Down that path lies madness. On the other hand, the road to hell is paved with melting snowballs.
Re:netscape! (Score:2)
Support the font*: tags in CSS1 correctly so my pages don't look like garbage on Linux boxen.
Product Differentiation vs. Standards, Simplicity (Score:2)
A related problem is that the Sun+Netscape Java Browser Conspiracy threatened to create a Runs-Almost-Anywhere programming environment that would make the underlying operating system mostly irrelevant, so software buyers and software users wouldn't have to care if they were using MacOS, Linux, FooBSD, Solaris, or those products from Redmond, which forced Microsoft to invade the browser market to keep from getting killed.
Support The AnyBrowser Campaign at www.anybrowser.org [anybrowser.org]
The browser wars at at fault. (Score:3)
What makes browsers suck now? Everyone who makes a browser is very reluctant to follow the path of the ones who won the war. I can think of a few examples - specifically a few that IE introduced to CSS standards that Netscape rejected, Mozilla implimented then broke or removed, and no other browsers will do. I'm referring to the :hover property. Is this feature a bad thing? Absolutely not! Better than making a big hacky JavaScript solution to do the same thing. But will any other browsers support this? No. That's just stupid - and it's not the only example.
Well, this post may jump around a lot and lack consistency, but I'm rushing to the point and I think the point is clear. Browsers suck because web developers want to use new technologies being developed by companies who build web browsers that introduce them. Then the other browsers refuse to adopt the new technologies - in several cases simply because the authors hate the company *coughMicrosoftcough* that introduced them. That's just stupid.
Logout (was Re:for you browser writers out there) (Score:2)
http://www.php.net/manual/en/features.http-auth.p
Which shows how to get browsers to forget, by sending a 401 status at them...
Hopefully this helps someone...
Re:It'd be nice... (Score:2)
Re:I think W3C missed one... (Score:2)
Actually, what the W3C recommends is that the browser FIRST check to see if the link works, then take you to the page. If the page isn't there, just display an error pop-up message.
--Chris ^^
darkstarpro.com [darkstarpro.com]
Re:"link" type considered harmful (Score:2)
I've been known to suffer brain farts when reading structured sites like documentation or other chaptered text where I think "I want to go and look at the last chapter" and I go and click on the back button taking me somewhere else. This usually happens when there is no navigation links constantly displayed in the window. (For example, in the common HTML rendering of the Linux HowTo format.)
One implementation I could see is that the browser could display a special toolbar with Next Section, Prev Section, Contents, Index, etc when it encounters these link types on a page. I can't be too hard to do -- for example Windows Help has a similar implementation where pages know about the site structure. (And sure, this problem could be solved by Frames, but why not present this knowledge to the browser and let it deal with it.)
Offtopic: 410 Gone (Score:2)
- j
Re:"link" type considered harmful (Score:2)
Sticking to standards (Score:2)
I'd say it does the right thing alot and guesses a lot less at what the developer was trying to do. But the way it looks to the average user is "This site works in IE, but not in Netscape, Netscape must suck." Usually its the page that sucks in my experience.
Now I think that somethings could be done better, but we get these developers who write everything only looking at IE and then when their code doesn't work in Netscape, again Netscape gets a bad rap. But doesn't Netscape hold developers to a higher standard than IE?
Re:Content-encoding (Score:2)
2. AFAIK almost no-one uses compressed HTML because of a Windows IE bug. Blame Bill.
Disagreements. (Score:2)
Netscape were doing well for a while - but they too had their dominance in the industry. They were so smug with what they ahd accomplished, they saw no need to improve. Communicator was an attempt to fight back at MS, who were building an impressive web browser. And, NS only went half-way with it. It was hardly anything new and impressive.
That is why we have the situation we have today. A lot of people liked (and still like) Netscape but were stuck with the 4.x browser because of MS's illegal business practices. So a lot of web developers had to develop for a bitrotten browser instead of making use of new standards like CSS (yes, NS4 had some sucky CSS support (so did IE 4)). Finally, everyone said "fuck it" and developed for IE 5.
Totally wrong. IE4 was probably the first browser to actually do CSS right. Now granted, IE2 and IE3 were worlds behind NS2 and 3 respectively, but IE4 is the one that sped away in the technology race. But you're only partially right on the issue of NS4 having some sucky CSS support... it had VERY sucky CSS support. Btw, you're comment about the hover function. Geez dude. Are you so myopic that you could only get that from the statement? The point was is there is a lot of very basic simple support that Netscape just neglected to product. Duh.
When MS won the browser war, it wasn't just NS who lost. We all did.
Pffft... You know, as a Linux user and open source advocate, the only things I find myself jealous of Windows users are their web browser and well design multimedia architecture. IE is so incredibly nice and it's such an excellent browser - faster, more stable, and cleaner overall. The only way we've lost is that we just don't get the source to IE and someday, that might even change. *shrug* Of course then again, I'm building my own technologies that are 100% browser independant (thankfully there's no conflicts over ECMA standards :-).
Buase of DOCTYPE is worse than no use at all... (Score:2)
Re:netscape! (Score:2)
when i look at some website, i'd like too see it just the same no matter what browser i am using. Pictures included.
You'll never ever fix pathological cases like this one, unless every browser uses the _same_ rendering code. (On the same hardware, for that matter...) You can always exploit differences in implementation.
are there still standards?
Sure! If you use conservative HTML 3.2, or even most of 4.0, you can show a page that looks nearly identical on most every browser. Oh, you want to use your new Java-Flash-PNG-Javascript-whizbang navigation system? Sorry. If you want nonstandard functionality, you have to take advantage of nonstandard features.
What people seem to have trouble understanding is that most sites that are "incompatible" with one browser or another are that way because of a _conscious decision_ on the part of the authors!
And I saw the elephant. Does that mean my browser "lost"? :)
Re:Good luck to them (Score:2)
Re:hmmm (Score:3)
Re:How about following the DTDs? (Score:3)
Then came <blink>. And <center> . And <font> and all hell broke loose.
Re:Good luck to them (Score:2)
Just to be clear, I think that it IS a good idea for somebody to have a rudimentary knowledge of HTML markup.
Regardless, I don't count on anybody having that knowledge. You liken the concept of HTML to the knowledge of the difference between the clutch and the accelerator. If you base your argument on this comparison, you're correct. However, the comparison is erroneous.
The functioning of a car is dependant on the proper use and understanding of the clutch and accelerator. There is no way to operate a car successfully if you don't know how to use them properly.
On the other hand, a Web page can be successfully navigated without the use of the keyboard at all, much less the need to type HTML tags. A "talkback" section can disallow HTML completely. You can function FOREVER on the Web without knowing how to type HTML tags.
The clutch/accelerator analogy is closer to the Back/Forward buttons on a browser window. Not knowing how to use those will stall you fairly quickly on a typical web site, just like the improper use of a clutch will. A more proper analogy for HTML tags to a car would be the wiring behind the dashboard that makes the radio or the spedometer light up. It's not complicated, and a few days spent studying it will familiarize you with how it works, but is completely unnessecary to the proper operation of the car.
Thus, my argument still stands -- why must we force non-mechanics learn the language of mechanics in order to write simple notes on a Web site?
What I find completely amazing... (Score:3)
- There is a clearly articulated definition of what tags are supported
- there is a clearly articulated definition of what the tags are supposed to do and how they are to be rendered
My question is why do so many browser not render correctly? What is so hard? One of the hardest parts of programming is requirements definition for the software being written, and getting the customer/boss to clearly articulate what they want the software to do and how it should perform. Once you have the iron-clad requirements written down, the rest of the work is a piece of cake - it is implimentation and testing against the requirements.
In the case of HTML, where there are clear definitions for 3.2 and 4.0, a list of what is deprecated and what is supported, if web page authors stuck to the STANDARD and not use browser specific tags, then there is no reason that the page should not display identically on each persons browser. I find it unfathomable that this is not the case.
Re:Slashdot gets it wrong again (Score:2)
I strongly disagree... Any webpage author should know in detail how web servers communicate and how web browsers interpret the data. I think that this document is important to everyone!
--Chris ^^
darkstarpro.com [darkstarpro.com]
Browser size (Score:2)
You shouldn't.
I think that scientific design says that the ideal width of text lines is not as long as possible. The eyes have to scan too many times horizontally. It is better to keep the number of scans per line to 2 or 3 (from memory).
So even when I have a big monitor, I don't maximize my browser window.
__
Re:Head up its ass. (Score:5)
Web designers need to remember that Web design is not print. Documents will be changed by users and users should have that freedom. Worry more about information architecture, it's the content that ultimately matters. Design shouldn't just be decoration that viewers have to conform to, design should help viewers to better comprehend the information they're seeing.
What about handicapped users? Or those who need larger type to see? What about celphone browsers? PalmOS? WebTV? Crappy WindowsCE appliances in the airport business lounge?
Web design extends traditional design towards architecture and engineering. Good Web design is flexible. It doesn't matter what the building looks like if it falls on your head.
Strict adherence to standards is the best thing we've got. Letting go of the bells and whistles is better for your clients, your audience, your bottom line and your sanity.
Re:ha! (Score:2)
Re:Bring back verbose loading! (Score:2)
I think the argument that browsers only say "Opening page..." is because that person is using Internet Explorer.
--
Re:hmmm (Score:2)
i don't know about you, but I get bit by web pages that have incomplete tags all the time. That, in the context of this recommendation:
1.7 Warn users about incomplete documents and transfers.
sort of like saying "it is not completely bad, just mostly"
I just get bent out of shape by MS abuse of the standards process.
pardon me.
Re:Bring back verbose loading! (Score:2)
Re:Other useful changes (Score:2)
This is actually already available in the browser I use daily; Opera (yes, it has some good ideas built into it too).
You can specifiy time periods for when it should check whether the document, image or "other" has been modified in days, hours, mins and also "always" and "never". I've seen it cache CGI-output and not bother to contact the server, which of course gives a blazingly fast loading of pages.
It's already been thought of, at least on the client-side, but not in one of the "major two" browsers.
I dont understand why a browser hasnt done this (Score:3)
Re:hmmm (Score:3)
Re:Bring back verbose loading! (Score:3)
That said, having an option "[ ] Show me details when downloading a page" would be great for those of us who can use the information.
Re:...and braille? (Score:3)
More advanced software for Windows writes what line is currently under the mouse pointer, provided it's text and not a graphic.
Re:hmmm (Score:5)
Too bad now that 99% of the surfers out there don't care about content, but instead want their flashy, bullshit "user experience" to make it easier for them to read the bullet points of the information they're looking for. When was the last time you actually *read* a page full of content, that wasn't marked up to hell and back. I'm not saying everything out there should be block text for pages and pages, of course
Sometimes I *do* want the web to go back to the netscape 1.0 days (tables! wow!) where everything was grey (well, 1.0 had bgcolor I guess, so pre-1.0 days) when you surfed the web for information, not "experience". If I wanted experience back then I'd go outside and take a walk, watch a movie, or whatever.
Don't hide 404 messages! (Score:4)
Saving content (Score:3)
--