I've heard no response to this; if there is no negative reaction, I'm going to open a JIRA for it (and submit the necessary patch).
Take care, Joey On 8/7/06, Joseph Rozier <[EMAIL PROTECTED]> wrote:
The Agent capabilities currently include the public height and width, but these properties are problematic. I propose the following: 1) if it is at all possible that an agent can have more than one height/width then these capabilities should not be hard-coded in the agent's capabilities .xml file (which they are today in some cases) 2) height/width should be defined as the resolution reported in the request headers, not necessarily the currently available height/width in the browser (in the case of Pocket IE, the User-Agent string includes the device resolution, for IE Mobile the resolution is reported in a UA-pixels header) Currently, the height/width capabilities are set in one of two ways: 1) Some PDA capabilties .xml files have hard-coded values for these properties. (e.g. see trinidad-impl\src\main\resources\META-INF\agent\pocketie.xml) 2) Some agents set these at runtime using the User-Agent string (the Industrial Telnet Server and the JDeveloper runtime) Most agents do not set these properties as far as I can tell. The hard-coded values do not make much sense in my opinion. Take the case of Pocket IE. For this agent, the height is hardcoded at 255 and width is 229. These precise-seeming numbers come from some MS documentation describing how much screen real estate is available to the browser on a typical 320x240 resolution device when you take away the toolbars/etc. It turns out many things can affect the screen size on Pocket IE: 1) You can view the browser "full screen", removing the toolbar and such 2) on some devices you can adjust the orientation so that height and width are reversed (e.g. some devices with sliding keyboards automatically switch orientations when the keyboard slides out) 3) some PocketPC/Windows Mobile devices have non-"standard" screen sizes, such as the iPaq 6900 which is 240x240 On other agents it's even more problematic. The BlackBerry Browser 4.0 runs on a wide range of devices, so choosing a single hard-coded height/width does not make sense. Pocket IE includes the full screen resolution in the User-Agent string. IE Mobile includes the full screen resolution in the UA-pixels header. I propose using this value (if available) to determine the agent height/width. If this value is not specified in a request header, then the values will not be set. Any thoughts? Take care, Joey Any thoughts? Joey
