124
edits
(→About Gecko: update this section, and make it into paragraphs to improve readability) |
|||
| Line 29: | Line 29: | ||
===About Gecko=== | ===About Gecko=== | ||
For Mozilla-based browsers, the rendering engine is Gecko, and “Gecko is Gecko”. Drivers, the group overseeing the Mozilla project, have taken a strong, clear stance that all Gecko-based browsers must support the same web technologies (''fn a list of these?'') in content area (regardless of whatever user interface or application features distinguish these applications in the mind of end-users). | For Mozilla-based browsers, the rendering engine is Gecko, and “Gecko is Gecko”. Drivers, the group overseeing the Mozilla project, have taken a strong, clear stance that all Gecko-based browsers must support the same web technologies (''fn a list of these?'') in content area (regardless of whatever user interface or application features distinguish these applications in the mind of end-users). | ||
For a given Gecko version (the rv: value part of a Mozilla-based browser’s user-agent string), all browsers have the same capabilities, support the same technologies, and have the same bugs '''in the content area'''. Given identical fonts and settings (and with the exception of form widgets and scrollbars, which adhere to the style of the operating system), all Gecko browsers sharing a Gecko major version (1.8.1, 1.9.0, 1.9.1, etc.) should render a given page '''identically''' (if you find this is not the case, this is a '''serious bug''' and should be filed in [https://bugzilla.mozilla.org Bugzilla]). | |||
Thus authors should sniff—'''if sniffing is absolutely required'''—for Gecko and a particular Gecko version instead of the application name. | |||
===Sniffing for “Firefox” : Bad === | ===Sniffing for “Firefox” : Bad === | ||
edits