Closed Bug 107495 Opened 23 years ago Closed 22 years ago

scrollbars #2 overflow scrollbar states

Categories

(Core :: XUL, defect)

Other
Other
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 12825
Future

People

(Reporter: rvj, Assigned: hyatt)

Details

Assuming that onoverflow/onunderflow are used to catch scrollbar visibility 
changes, there needs to be a property/attribute that indicates the dynamic 
state of the scrollbars

e.g. verical, horizontal, none, both

These values can then be used to hide 

a)the appropriate static scrollbar if the overflow:scroll option is used,
b) to hide the thumb if no scrolling is possible

Currently getAttribute(style)only returns the static CSS style setting, not the 
dynamic state

Apologies if a property exists, but no response from newsgroup. If there is 
already such a property, please do tell!!
Summary: overflow scrollbar states → scrollbars #2 overflow scrollbar states
or .......

should (does) the scrollbar height and width properies always reflect ACTIVE 
scrollbar visibility?  i.e. where zero equals collapsed

in this way if an element generates an overflow event then it might be possible 
to use two scrollbar methods ( to return current height and width )to check 
scrollbar visiblity


Because xml and htm have different methods for determining content length and 
width, it appears that pageYOffset and pageXOffset provide the only general 
means of determining ACTIVE scrollbar visibility.

I have (an awful) workaround which requires scrolling the current content by 
one pixel and then checking the new offset value. If the new value is zero 
then  no scrollbar is displayed. In non-zero then the content has scrolled and 
needs to be reset back to its original value.

The problem here is that the checking is done via the onoverflow or underflow 
event. The process of restoring the original value at document extremities may 
cause unpredictable effects ( an infinite loop of scroll tests)

Is there a  simpler javascript test???

If not then a Mozilla API call ?????
testcase?
Target Milestone: --- → Future
Status: UNCONFIRMED → NEW
Ever confirmed: true

*** This bug has been marked as a duplicate of 64029 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
wrong dupe
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---

*** This bug has been marked as a duplicate of 12825 ***
Status: REOPENED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → DUPLICATE
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.