Last modified: 2008-07-14 14:56:42 UTC
BUG MIGRATED FROM SOURCEFORGE http://sourceforge.net/tracker/index.php?func=detail&aid=980991&group_id=34373&atid=411192 Originally submitted by Tomos (wiki_tomos) 2004-06-28 06:11 It is reported that with Monobook skin, saving a text using Pocket IE (that is a browser that comes with PocketPC2003). The save button is hidden by the edit box. The copyright warning, which is legally an important part of what users are required to agree, is also hidden. A screenshot is here: http://ja.wikipedia.org/wiki/%E7%94%BB%E5%83% 8F:Ppc_henshu.png ------------------------- Additional comments ------------------------ Date: 2004-06-28 11:54 Sender: SF user gabrielwicke Fairly weird layout it produces- something very different from what the css rules specify. I'm inclined to blame it all on the Browser.. Does it use the css rules at all? There should be no tabs at the top if it doesn't. If it does, a special handheld stylesheet might be necessary for IE. You can experiment with special rules in you user css like this: @media handheld { #column-one, #p-cactions, #p-personal { position: fixed } }
*** Bug 105 has been marked as a duplicate of this bug. ***
I'll mark this "fixed-in-cvs" because there's the Chick skin for Pocket IE now. However, as long as the mere use of Pocket IE doesn't trigger Chick being used as the default skin, this is arguably not a fix.
Would Pocket IE honour @media handheld?
Removing fixed-in-cvs keyword.
I don't think that the PocketIE (at least before Windows Mobile 2003) does honour @media handheld, as it's part of CSS 2.0. Reference: http://blogs.msdn.com/windowsmobile/articles/213771.aspx A (possibly good) workaround/hack would be to check the browser's identification string and inject another stylesheet when a PocketPC IE was found.
IE browsers generally support conditional stylesheets through an HTML/XHTML comment hack. Monobook already uses this for many stylesheets. If PocketIE does, then PocketIE problems can be solved the same way as desktop IE problems.
A few minutes of Google searching doesn't turn up any documentation on such. No documentation and nothing to test with makes it rather difficult to do anything about this...
No response from person originally opening bug. No activity since June 2006. Difficult to reproduce due to specific software being difficult to get hold of. Closing as INVALID.
