Closed Bug 375620 Opened 13 years ago Closed 11 years ago

input buttons inactive on page generated with CSS and nested div

Categories

(Core :: Layout, defect)

1.8 Branch
x86
Linux
defect
Not set

Tracking

()

RESOLVED DUPLICATE of bug 102695

People

(Reporter: victorchurchill, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.2) Gecko/20061201 Firefox/2.0.0.2 (Ubuntu-feisty)
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.2) Gecko/20061201 Firefox/2.0.0.2 (Ubuntu-feisty)

The two urls: http://83.138.142.10/html/afterbug.html and http://83.138.142.10/html/beforebug.html differ only by one line:
<div><div>some stuff with buttons</div><div>stuff2</div>
When the second div has no content, the buttons appear fine. When some content is put into the 'stuff2' area, all buttons before that stuff become inoperative. Subsequent buttons still work.
The example is a html save from a dynamically generated page.


Reproducible: Always

Steps to Reproduce:
1.go to the 'beforebug' exam[ple.
2. the buttons in all sections 'work'.
3. go to the 'afterbug' example.
4. the first 2 sets of buttons are dead but the third are OK.
Actual Results:  
In the 'after' example, the HTML for the buttons and div structure is as beforebut the buttons are inoperative.


Happens in FF2 on WinXP as well as on Linux.
Component: General → Layout
Product: Firefox → Core
QA Contact: general → layout
Version: unspecified → 1.8 Branch
Because #infoview-graph is relatively positioned, it's stacked above the buttons.

Actually, that shouldn't cause problems, but there's a bug that doesn't let you click the buttons in this case.

I saw the report this week, but can't find it ATM.
Whiteboard: DUPEME
There it is, sorry for spam.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 102695
(In reply to comment #2)
> Actually, that shouldn't cause problems, but there's a bug that doesn't let you
> click the buttons in this case.

The bug in question is probably invalid, although we'll probably implement the 'pointer-events' CSS property at some point to let you choose other behavior.
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.