You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the CSS rules on line 113 (.resize-triggers > div { overflow: auto; }) causes Safari to set overflow on contract-trigger and expand-trigger to auto, obviously. When used with a scrollable div, Safari gives these two divs a smaller width (because of the overflow: auto generates space for an invisible scrollbar) This causes the vertical scrollbar on the div to be un-clickable.
As a fix, I simply removed the overflow: auto rule from the plugin, but am now obviously worried about unknown side-effects. What was the original purpose of this rule?
I'll try to attach a jsbin or something ASAP.
The text was updated successfully, but these errors were encountered:
I've also run into this issue. An alternative I'm testing is adding the .resize-triggers element to the first child of the parent element (rather than the last child like is currently).
This seems to achieve the same outcome (Safari's scrollbars don't block clicks from the other content.
One of the CSS rules on line 113 (
.resize-triggers > div { overflow: auto; }
) causes Safari to setoverflow
oncontract-trigger
andexpand-trigger
toauto
, obviously. When used with a scrollablediv
, Safari gives these twodiv
s a smaller width (because of theoverflow: auto
generates space for an invisible scrollbar) This causes the vertical scrollbar on the div to be un-clickable.As a fix, I simply removed the
overflow: auto
rule from the plugin, but am now obviously worried about unknown side-effects. What was the original purpose of this rule?I'll try to attach a jsbin or something ASAP.
The text was updated successfully, but these errors were encountered: