Re: Firefox \ Iceweasel Differences?



On 07/31/2007 09:30 AM, Andrei Popescu wrote:
IIUC websites shouldn't care about/need to know what browser is
used, as long as they are following the standards.

You do understand correctly, but emphasis must be placed on the
word "shouldn't". Websites *should* not need to care or know
about what browser is used.

However, even following the standards, any site that reaches a
moderate level of design complexity will have issues on different
browsers.

As a programmer, I feel icky having to tailor a site to different
browsers. It feels like a "hack" to me, and I hate hacks. Instead
I do the following:

1. Change the design so I do not have the problem.
2. Accept that it will not display the same on all browsers.
3. Make sure it if functional on all browsers.

--
Glen


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx



Relevant Pages

  • Re: langua= vs type=
    ... no 'correct' MIME type to accept). ... current browsers will have no idea what to make of the new official MIME ... >>> depending on the script. ... > My gander is raised by those that scream "STANDARDS" and beat their ...
    (comp.lang.javascript)
  • Re: Problem with submit in IE and FF
    ... Optimizing for a limited set of browsers instead of applying Web ... standards in order to optimize for a wider set of sufficiently standards ... and the IE debugger halts on it, but the Firebug ... Either server-side (displaying the request variables via JSP) or in Firefox ...
    (comp.lang.javascript)
  • Re: HTML (WAS: MF having issues?)
    ... write HTML in MS Word... ... Secondly, although I may have issues with COPBOL standards, the W3C is ... as well as getting DW to check for various Browsers. ... render text in italics because that's how your particular browser visually ...
    (comp.lang.cobol)
  • Re: Accelerated legacy code
    ... lots of code which doesn't fit new standards, ... One example is a CRM/ticket system that only works with IE6. ... TOO hard to check things across Browsers (although it is definitely extra ... Windows Server 2008, Linux, or MacOS. ...
    (comp.lang.cobol)
  • Re: Website built in Frontpage 2003 looks bad in Chrome & FF
    ... " I thought that with the new generation of browsers there would be some ... there are standards - but YOU have to code to them. ... Your own code is curious- lots of potential CSS there, but there is one error repeated so many times it would be easier to start again than correct. ... The other mode - Quirks - means that IE will follow the rendering rules that IE5 follows, and FireFox will follow a different set of rules. ...
    (microsoft.public.frontpage.client)