Browser remedies, bugs, and Solutions (Part III)

Solution | Browser

Mozilla family/gecko

When the browser Battle of the last century drew to a close, Microsoft's IE had actually won, and Netscape announced its browser to open the source code and set up a Mozilla organization. The Mozilla Group has abandoned most of the code for all Netscape Navigator, rewriting the engine. It was a tough process, and Netscape had not been able to release its new browser in the quickest possible time, so that IE had been alone for years. Netscape, after being acquired by AOL, has published 6.x, 7.x, 8.x browsers on the basis of Mozilla. But in addition to loyal fans, plus Mozilla's main push for Firefox, no one knows them anymore.

Mozilla is a large suite that includes browsers, mail clients, IRC chats, and even a Visual Web editor. The complex system scares the user who needs only the browser. In order to perform their duties, Mozilla has spawned browser Firefox, mail client Thunderbird, and web editor has a nvu on the basis of preserving the Mozilla suite. They are based on the same render engine gecko. Based on this engine browser and Linux under the Epiphany, Galleon,mac under the Camino and so on. It is customary to call them the Mozilla family (Mozilla Family).

Because this chapter involves less content (they are basically perfect, no bugs can make me increase the number of words), I prefer to talk about history, MO:). Firefox in the name also called Firebird, Phoenix has attracted the attention of CSS designers. The Gecko engine is very close to the rules of the CSS3, and there are a lot of new features that make designers excited. But there are still some little quirks, but they can be corrected right away, just think of the trident that hasn't changed in 5 years ...

I'm announcing that the current version of Gecko doesn't have the ability to affect the design bugs in CSS ...

Safari

After the release of Mac OS 10.3 (Pather) in 2003, Safari became the default browser. Its engine is called WebCore, based on the open source project KDE under the Konquerer khtml engine. With the release of Mac OS X 10.4 (Tiger) in 2005, Safari 2.0 became the first browser to pass the Wasp Acid2 test (official release). Although 1.x has a lot of bugs and quirks, however, the phrase, non IE users are willing or unconstrained to upgrade their browser, the following only gives the known Safari 2.x bugs and solutions.

Safari 2.x Bug and solution List Bug Solution

The fieldset settings display: inline; will make the form not clickable.

Relative positioning fieldset :

fieldset {display: inline;position: relative;}

Using :hover an adjacent selector of a pseudo class causes the wrong behavior:

dt:hover + dd {color: green;}

No solution at present

when you enlarge a font, the resulting content causes the text to go beyond its box range.

No solution at present

Opera

In history, opera also has some CSS quirks, which may be to imitate IE behavior. But the new version of the performance is very good, desktop version since 2005 9 years 8.5 released completely free (remove ads), and mobile version of the mobile phone market, so it is also a fresh force in the market. The development of opera itself has a number of international standards of the writers, technical experts, so opera's support for the standard absolutely let you satisfied.

Opera 9, a recently released version, uses the engine called Presto, and passes the ACID2 test.

I declare that the current version of opera (9.0+) does not have the ability to influence the design bugs in CSS ...

No sword in hand, no sword in Heart

Similarly, the highest level of hack is that there is no hack. Our series of articles, the first two parts are talking about ie. Let's take a look at an interesting picture:

It can be found that contemporary web design, the problem most of the time spent on IE. We are surrounded by a lot of better browsers, designed for them is also an easy thing, then, can you make IE independent? Yes, treat the browser differently and make the "patch" CSS visible only to inferior browsers. Inferior? Yes, you know, I mean ie5+/win. In this way, we can focus on the design, implementation, and in the later focus on the solution IE problem. And so we don't have to use hack (of course, trick) or something that could lead to chaos and all that mess ... What, what do you write about the two parts of your previous job?

We can certainly use JavaScript or other techniques to identify browsers, but we have a more secure approach. First, let's look at the source code of vitamin, and we can find this paragraph:

<!--[if lt IE 7]><link type="text/css" media="all" rel="stylesheet" href="/css/main_IE.css" /><script type="text/javascript" src="/scripts/pngfix.js"></script><![endif]-->

The things in the comments are only less than the version 7 of IE, which other browsers ignore. Thanks to MS, once again bow to the Pacific direction ... To learn more about conditional comments, check out the MSDN documentation.

Even if we do not care about IE 6 and the following version of the browser, we do not engage so many hacks or tricks, directly with/ie7/(this is not IE7, is a js) forget. Although the efficiency is a bit of a problem, hehe, let ie blame it ... But basically is impossible, especially in China environment, everybody takes ie to take care of well ...

Well, we're done with this series. I hope IE7 can come out quickly and popularize, although not perfect, but enough can make life more comfortable. The Web standard itself is not complex, but the current IE6 and other browsers on the lack of CSS support and misunderstanding, the need to hack things too much, so that beginners mistakenly think very advanced ... I hope that in the future no longer need to hack, no more trick, do not need a division of the page, each Web designer can personally fencing, well, I can also be unemployed ... Xd