Closed
Bug 523037
Opened 15 years ago
Closed 14 years ago
<maction> child drops below the line
Categories
(Core :: MathML, defect)
Tracking
()
RESOLVED
FIXED
mozilla1.9.3a5
People
(Reporter: catalindavid2003, Assigned: fredw)
References
()
Details
Attachments
(3 files)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20091007 Ubuntu/9.10 (karmic) Firefox/3.5.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20091007 Ubuntu/9.10 (karmic) Firefox/3.5.3
We are working on creating "active" documents, providing a user interface by which the user can change the content of a pre-fetched file.
Therefore, for example, when testing the unit conversion, if the JavaScript code behind modifies the document in order to create new children under the <maction> tag, the new content that is added will appear one level under the normal height of the text, as if it were on the next row.
Reproducible: Always
Steps to Reproduce:
1. Right click on the 100 metre element (be careful to move the mouse in the upper right corner -- jQuery bug)
2. Select convert to miles
3. Wait... the webservice providing this data is very slow
4. When the new <maction> child is created, it will be displayed under the current level of the line it should belong to.
Actual Results:
The new child (result in miles) is one level under the normal flow of the text.
Expected Results:
The <maction> child should be at the same level.
Assignee | ||
Comment 1•15 years ago
|
||
This is quite difficult to reproduce. Sometimes, javascript errors are reported. A reduced testcase would help to understand what is happening.
Reporter | ||
Comment 2•15 years ago
|
||
This is a sample testcase where nested maction-s result in text being displayed in a weird way, as if it were on a new row.
Assignee | ||
Comment 3•15 years ago
|
||
Thanks for the testcase, I've reduced it any further.
Assignee | ||
Updated•15 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•15 years ago
|
Assignee | ||
Comment 4•14 years ago
|
||
Fixed by the patch of bug 556767.
Assignee: nobody → fred.wang
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•14 years ago
|
Target Milestone: --- → mozilla1.9.3a5
You need to log in
before you can comment on or make changes to this bug.
Description
•