A
A
Artqookie2011-03-24 18:27:38
HTML
Artqookie, 2011-03-24 18:27:38

Different layout for browsers

There are some interesting downsides to this approach. We determine the user's browser and, depending on it, we give the layout without hacks, etc. for this browser. What could be the catch here?

Answer the question

In order to leave comments, you need to log in

6 answer(s)
A
Alexander, 2011-03-24
@Palehin

The user can change the user-agent himself, therefore, the given layout may not be suitable for the browser

A
alexbeep, 2011-03-27
@alexbeep

Some kind of pipe. For the last 3 years I have been using one(!) hack in total for IE<7. And one more thing - if you need to support PNG with an alpha channel ... That's all

I
Innsbrook, 2011-03-24
@Insbrook

With this approach, it is important to consider that the browser version is also determined for the nearest future versions of browsers. Sometimes I encounter the fact that after installing the latest versions of browsers, some sites show messages that I have a very old browser.

W
Wott, 2011-03-24
@Wott

There will be a problem with the cache - you will have to enter the user agent into the keys
Well, with support - several options are very hemorrhoids

K
Kane, 2011-03-25
@Kane

Why would you want to maintain more code? Developers can shape the future of the web on their own, but as long as we sharpen the layout for browsers, their manufacturers will dictate their terms to us. Why ms move with standards support, if everything works for end users anyway (thanks to hacks)?
In general, I don’t see the difference between using hacks and a separate layout for the browser. I think it's exactly the same hack.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question