Nu ben ik niet zo heel into deze zaken, maar AFAIK trekken juist de handhelds zich weinig aan van deze css media types maar correct me if I'm wrong. Dit is wat ik er 'in a glance' over kon vinden:
Opera Mobile
* One of the most popular and common handheld browsers. Installed by default on a very high number of phones and PDAs.
* Has a very high level of CSS support.
* Uses handheld media, if you specifically target handheld media (so you must actually say 'handheld', and not 'all').
* Supports media queries.
* Uses screen media if handheld media is not specifically targetted. The page will then be reformatted to fit the screen, so very little of the CSS will actually be used.
* Allows the user to disable reformatting if they want to, so they can see the page rendered as if it were on a desktop.
* Will not use handheld media on high resolution devices, but can still be targetted using media queries.
* Can be treated as a handheld browser.
Opera Mini
* One of the most popular and common handheld browsers. Installed by default on several phones.
* Designed to run on devices with the smallest screens and lowest capabilities.
* Has a very high level of CSS support in Opera Mini 4 on high capability devices.
* Uses handheld media, if you specifically target handheld media (so you must actually say 'handheld', and not 'all').
* Supports media queries.
* Uses screen media if handheld media is not specifically targetted.
* In Opera Mini 4 on high capability devices, tries very hard to behave like it is on a desktop (including using a virtual screen width), using a mouse. Text will be wrapped (and their containers extended as needed) to make the text fit the width of the screen.
* In Opera Mini 3-, or in Opera Mini 4 on low capability devices, or in Opera Mini 4 on high capability devices if the user has chosen the option, the page will then be reformatted to fit the screen, so very little of the CSS will actually be used.
* Can be treated as a handheld browser.
NetFront/Blazer
* One of the most popular and common handheld browsers. Installed by default on a high number of phones and PDAs.
* Has a reasonable but not good level of CSS support.
* Uses screen media, and cannot be targetted using CSS media types. The page will then be reformatted to fit the screen.
* Some special custom versions use only handheld media, and will ignore any stylesheets that do not specifically target it, meaning that most pages remain completely unstyled. They also ignore images on many pages. However, these versions are not very common.
* Has a broken implementation of @media rules; it often applies styles from any media type (such as print media), ignoring the media declaration.
* Allows the user to disable or alter reformatting if they want to, so they can see the page rendered as if it were on a desktop.
* Should be ignored as a handheld browser. Treat it as a desktop browser, and hope that its reformatting can be adapted by the user into something readable.
Pocket Internet Explorer
* Not very popular. Installed by default on Pocket PC and Windows Mobile devices, but is usually replaced with Opera or NetFront, as they generally perform much better.
* Has a poor level of CSS support.
* Uses handheld media and screen media at the same time (breaking the rules of CSS). The page will then be reformatted to fit the screen, so very little of the CSS will actually be used.
* Only understands media="..." attributes, not @media or media in @import rules.
* Sometimes uses @media blocks, but not reliably - ignored on most pages. May ignore an entire stylesheet if it contains media queries (not normal @media blocks).
* Allows the user to disable or alter reformatting if they want to, so they can see the page rendered as if it were on a desktop (apart from the obvious CSS limitations).
* Can be treated as a handheld browser, as long as you only apply the stylesheet in a way it understands, and you only use the method of overriding styles, since it will always apply screen media.
Series 60 Browser and Safari on iPhone
* Installed by default on the newest Nokia Series 60 phones. Not popular yet.
* Has a fairly high level of CSS support, as it is based on the Safari engine.
* Uses screen media, and cannot be targetted using CSS media types. Tries very hard to behave like it is on a desktop (including using a virtual screen width), using a mouse, and virtually no reformatting.
* Some newer releases support media queries.
* Should be ignored as a handheld browser. Treat it as a desktop browser, and hope that it works.
Minimo
* Still in very slow development. Not popular.
* Has a fairly high level of CSS support, as it is based on the Gecko engine.
* Uses screen media, and cannot be targetted using CSS media types. The page will then be reformatted to fit the screen, so very little of the CSS will actually be used.
* Allows the user to disable reformatting if they want to, so they can see the page rendered as if it were on a desktop.
* Should be ignored as a handheld browser. Just hope that its reformatting works.
Konqueror Embedded
* Still in very slow (virtually non-existent) development. Not popular.
* Has a fairly high level of CSS support, as it is based on the KHTML engine.
* Uses screen media, and cannot be targetted using CSS media types. The page will not be reformatted. Uses a mouse interface.
* Should be ignored as a handheld browser. The lack of reformatting means that most pages do not work.
OpenWave
* Fairly popular handheld browser. Installed by default on a number of phones.
* Has problematic CSS support (seems to have problems mixing class selectors and ID selectors, for example).
* Does not treat media queries correctly either as a media query, or with CSS error handling (required for browsers that do not support them). It may apply the rules inside them even if the query would not match the current situation.
* Uses handheld media. The page will then be reformatted to fit the screen.
* Can be treated as a handheld browser.
Obigo
* Installed by default on a some phones.
* Has relatively good CSS support in development versions.
* Uses handheld media if it is available.
* May use screen media if handheld media is not specifically targetted. The page will then be reformatted to fit the screen.
* Allows the user to disable reformatting if they want to, so they can see the page rendered as if it were on a desktop.
* Can be treated as a handheld browser.
* Insists that Web developers must pay to test their sites in it.
Deep Fish
* Still in closed alpha development, not available for testing yet.
* Possibly related to Obigo, which became part of a partnership deal with the parent company just before Deep Fish was announced.
* Media types unknown, but the demonstration images seem to use screen media.
* Uses a virtual screen width instead of reformatting.
* Probably cannot be treated as a handheld browser.
ThunderHawk
* Not popular.
* Apparently uses handheld media, but I cannot test this.
* May use screen media if there is no handheld media, but uses a virtual screen width instead of reformatting.
* Probably can be treated as a handheld browser.
* Insists that Web developers must pay to test their sites in it.
Picsel
* Not popular.
* Media types unknown, but the demonstration images seem to use screen media.
* Uses a virtual screen width instead of reformatting.
* Probably cannot be treated as a handheld browser.
* Only delivers to phone manufacturers and network operators, so not available for normal Web developers to test.
As well as the proper browsers, there are some others that are still in use, but are more of a left-over from the early days of mobile browsing.
Limited HTML browsers
These are sometimes installed as the default browsers on phones, but are being replaced with proper Web browsers. They do not understand HTML or CSS well enough for you to target them, and should generally be ignored. If they happen to be able to use your page (which they should if you use semantic HTML), then that is a bonus.
WAP/WML browsers
These are sometimes installed as the default browsers on phones, but are being replaced with proper Web browsers. They choose not to provide access to the full Web, and demand that authors waste time and resources by making an extra version of all of their pages. I ignore these completely.
XHTML browsers
These are like WAP browsers, but are able to use a small percentage of real Web pages, if they use XHTML. They are also being replaced with proper Web browsers. I ignore these as well.
Dus hoewel het 'in a perfect world' wellicht een oplossing zou zijn, lijkt het vooralsnog niet dé oplossing te zijn.
Overigens, op diezelfde pagina zie ik ook eerder aangehaalde punten:
* Handhelds have a small screen. Sizes may vary from 100 pixels wide, to over 500 pixels wide. Designs based on positioning or floats generally do not work, and neither do large margins, paddings, fonts, or images. Adverts in particular are problematic.
* Handhelds do not have a reliable pointing device. No Web page should ever force a user to use a mouse, but especially with handhelds, this cannot be relied on. Most handhelds do not have any kind of pointing device, and will simply allow the user to focus links or form inputs, one at a time. Some, but certainly not all, may allow the user to also focus mouse event targets. Some may be able to use a stylus, but these only touch the screen one tap at a time, and cannot be used for continuous hover effects, such as pure CSS menus. Only a tiny percentage of device browsers use a mouse pointer, but these are controlled very clumsily using keys, and cannot be reliably used for control either.
* Handhelds do not usually have a complete keyboard. They do not usually have modifier keys (Ctrl/Alt/Shift), and may have a limited keypad with very few keys, often requiring multiple keypresses to get one character. In general, they do not fire key events when typing, and may not actually retain focus on an input when typing (typically using a dialog that is not controlled by the browser). In some cases, they may have a fairly complete keyboard, but these will be missing keys like F1, and are still relatively awkward to use. Web pages that rely on keyboard events or access keys are generally not suited to handhelds.
* Handhelds do not like frames or scrollable areas. In many cases, the lack of a pointing device is what causes the problem, and it is very difficult to focus and scroll another frame. Some browsers can only show one scrollbar - on the edge of the screen.
* Handhelds usually have low bandwidth connections, and not much memory to store Web pages in. Web pages that use lots of images for decoration or content are not welcome.
[
Voor 108% gewijzigd door
RobIII op 06-10-2008 18:06
]
There are only two hard problems in distributed systems: 2. Exactly-once delivery 1. Guaranteed order of messages 2. Exactly-once delivery.
Je eigen tweaker.me redirect
Over mij
:strip_icc():strip_exif()/u/43400/avatar.jpeg?f=community){kind=avatar}
Verder is een touch-screen interface nét iets anders dan iets wat je bedient met muis (en 101-keys tobo). En los daarvan: de bandbreedte op die dingen is vaak veel kleiner dus je wilt zoveel mogelijk meuk achterwege laten om bandbreedte te besparen en je dus te focussen op de belangrijkste zaken.:strip_exif()/u/25820/raptorsafari.gif?f=community)
:strip_icc():strip_exif()/u/50085/reaperavatar.jpg?f=community){kind=avatar}
(overigens kan uiteraard een flexibele breedte gebruikt worden, maar dit wordt doorgaans verkeerd gebruikt of is verreweg minder mooi dan fixed width)
:strip_exif()/u/63834/MeAngry-NewSmall.gif?f=community)
:strip_icc():strip_exif()/u/94571/mashimaro.jpg?f=community){kind=spacer}
:strip_exif()/u/80759/monstermania_small.gif?f=community)