Opened 9 years ago

Closed 9 years ago

#11730 closed defect (wontfix)

BorderContainer: splitter, handle separates from gutter

Reported by: samduke474 Owned by:
Priority: high Milestone: tbd
Component: Dijit Version: 1.5
Keywords: BorderContainer Splitter Chrome Cc:
Blocked By: Blocking:

Description (last modified by bill)

In Google Chrome, clicking the BorderContainers splitter while zoomed not at 100% causes the gutter to separate from the splitter 'button' as well as increasing the gutter size initially. If zoom is above 100%, the gutter movement is away from the "center" region, while the splitter 'button' remains under the mouse. Below 100%, the gutter moves the opposite direction.

Not sure if this is due to a higher DPI on this machine.

After zooming in and then out, the splitter returns to its proper home.

The problem can be seen to a lesser extent in Firefox by zooming in (ctrl +) a lot and then clicking the splitter a few times, a separation of a few pixels appears. Not sure if this is related.

I think the picture attached shows this best.

Interestingly, ExpandoPanes? do not have this problem.

Attachments (1)

splitterproblem.png (39.3 KB) - added by bill 9 years ago.
screenshot

Download all attachments as: .zip

Change History (5)

comment:1 Changed 9 years ago by samduke474

I can't upload the file I have, but here is a link to the picture:

http://img96.imageshack.us/img96/1336/splitterproblem.png

Changed 9 years ago by bill

Attachment: splitterproblem.png added

screenshot

comment:2 Changed 9 years ago by bill

Description: modified (diff)
Summary: BorderContainer splitter, handle separates from gutterBorderContainer: splitter, handle separates from gutter

Ugh, I see what you mean, webkit's zoom has a lot of issues, see also #10959. I tried the latest chrome beta and it's still broken.

comment:3 Changed 9 years ago by samduke474

I should also point to this which I am following: http://code.google.com/p/chromium/issues/detail?id=679

there are problems with the zoom that are (slowly) being fixed. I wonder if there is any sanity check that can be done in BorderContainer? to confirm the correct positioning or if webkit reports things improperly

comment:4 Changed 9 years ago by bill

Resolution: wontfix
Status: newclosed

This problem is lessened in Chrome 8, although not completely fixed. Still, I think we just need to wait for chrome to fix their bug, because I don't know how to workaround the problem. Patch welcome, but for now I'm going to close this as wontfix.

Note: See TracTickets for help on using tickets.