New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firefox 11 does not render first menclose correctly #212
Comments
This bug should have been detected by tests like (or other menclose-1*) but apparently that's not the case. If it's a timing issue, maybe using the testing framework avoids it. |
I don't remember what version of Firefox you used for the tests. It is new in Firefox 11. Many of the menclose notations are handled using SVG, and since it is only the first one that causes problems, I'm wondering if it has something to do with starting up SVG within Firefox. Perhaps in the tests, SVG had already been used and so the examples worked out OK. Alternatively, some of the menclose notations don't use SVG, so if it is some timing issue with loading menclose.js and SVG, having one of the non-SVG notations first might avoid it. I haven't looked at the test, but you might try starting with circle as the first one. |
Each notation is tested in a separate file. Here is the test for "circle": |
Setting "QA - Testcase Wanted" as the unit test above does not seem to detect the issue. |
I'm still not able to reproduce the issue. I tried with several |
Davide, any update on this? |
I haven't tested it lately. I know I did see it at one point, but that was quite a while ago. |
I've never been able to reproduce this issue. I guess we can close it if you don't see it any more. |
Closing the issue. |
The first
<menclose>
element that requires SVG output doesn't render properly in Firefox 11 (but does in previous versions of Firefox) in HTML-CSS output. Subsequent instances of the same<menclose>
statement render correctly. Seems like it might be a timing issue either with loadingmenclose.js
or with some initialization that Firefox is doing. Needs more investigation.The text was updated successfully, but these errors were encountered: