Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 351218

Summary: Improve support for browser-zooming on runtime
Product: [RT] RAP Reporter: Tim Buschtoens <tbuschto>
Component: RWTAssignee: Project Inbox <rap-inbox>
Status: ASSIGNED --- QA Contact:
Severity: enhancement    
Priority: P3 CC: flavio.donze, sgouta2, tbuschto, webmaster, wian
Version: 1.5   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Tim Buschtoens CLA 2011-07-05 12:15:00 EDT
Zooming an application on runtime (e.g. with ctrl +/- ) can result in layout glitches, in addition to glitches that might appear if the application is loaded while already zoomed in/out (i.e. not 100%). That is probably because the results of textsize measurements vary slightly on each zoom-level.
Comment 1 Tim Buschtoens CLA 2011-07-05 12:33:09 EDT
To prevent these issues, the zooming first has to be detected. I could not find a bulletproof way to do so using the browsers window or document objects. However, it should be possible to detect the changes in textsize, by comparing the result of the measurement of the same string every time the clientHeight/clientWidth values change.

If a zoom has been detected, all textsize-dependet layouts have to be recalculated. These are, on one hand, the purely client-side elements, mostly the text-elements within Buttons, ToolItems, MenuItems, etc.. Since most (not all) of them are based on either MultiCellWidget or Atom, that task is managable, though somewhat intricate.

On the other hand, since the server also stores textsize information, this data and the layouts that depend on it have to be updated also.
Comment 2 Markus Krüger CLA 2012-09-03 04:48:07 EDT
Is there anything planned regarding this bug?
Comment 3 Tim Buschtoens CLA 2012-10-26 13:28:36 EDT
Sorry, missed that comment.

Currently not, since i'm not really happy with the solution is described, and it would be a lot of work. I think this is comething for 2.1, at the earliest, unless someone wants to provide a solid patch.
Comment 4 Ivan Furnadjiev CLA 2013-06-28 04:18:04 EDT
*** Bug 370755 has been marked as a duplicate of this bug. ***