Ticket #170 (closed Tasks: fixed)
Implement BrowserField2 for OS 6.0
Reported by: | octo | Owned by: | octo |
---|---|---|---|
Priority: | normal | Milestone: | 2.0 |
Component: | LogicMail | Version: | None |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
The current method of displaying HTML messages involves a somewhat awkward and difficult-to-use "BrowserField". This field is an older version of the device web browser engine made available through a cumbersome API.
OS 5.0 has an entirely new "BrowserField" implementation: net.rim.device.api.browser.field2.BrowserField
This new field should be used for HTML message display on OS 5.0 devices.
Change History
comment:5 Changed 8 years ago by octo
Current updates only implement this on OS 6.0, and it might wind up staying that way. I haven't decided for sure yet.
There are still some lingering issues that may need fixing, if I can figure out simple ways of doing so:
- Vertical screen-swipe scrolling doesn't work, but the touch-pad can be used as a workaround (only a major concern if 5.0 support is added, or if non-touchpad 6.0 touchscreen devices are released)
- HTML messages that are wider than the screen may actually be commonplace, and annoying
- Can be fixed with annoyingly-tiny-text auto-zoom-out
- Can be fixed by attempting to inspect and alter the DOM tree to change hard-coded pixel-widths
- Zoom in/out hotkeys may conflict with normal message-viewing hotkeys on certain devices and keypad locales
- Currently, zoom hotkeys are only checked if no other hotkeys are matched
- Workaround may have to involve explicit field-focus-detection for hotkey processing, and may get in the way of expected hotkey behavior
Note: See
TracTickets for help on using
tickets.