On Sun, Dec 07, 2003 at 09:17:18AM -0800, Allan Anderson wrote: > But surely the other side of the argument is worth considering: that > encouraging standards will result in a WWW and software that works > better together, thus making software do what users expect.
Users should at least be given the option of rendering the page once it's loaded in the browser, and is obviously HTML. > Old arguments on both sides. But where to draw the line, and should > Camino deviate from the Mothership of Mozilla policy? It depends on how it's implemented. If it's by sniffing the content and rendering based on the results, then it should be done in Gecko. However, if there was a menu item that says "Render this page as HTML," after the page is loaded, then it could be done in Camino. I've filed a bug to add a menu option for rendering a page once it's been download: http://bugzilla.mozilla.org/show_bug.cgi?id=227731 Since all bugs that are filed in favor of rendering text/plain are automatically closed as WONTFIX, I think that this is the best chance we have for getting this type of functionality. Adding an option to render the page after the fact doesn't violate the HTTP standard, so it is more likely to be implemented. We can work on getting an option for this to be default behavior after we get basic functionality built in. -- GPG public key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x9D5B8762 _______________________________________________ Camino mailing list [EMAIL PROTECTED] http://mozdev.org/mailman/listinfo/camino
