Closed
Bug 1137661
Opened 11 years ago
Closed 11 years ago
Performance issues with nested flexboxes
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: hello, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36
Steps to reproduce:
I've posted test code and demo here: http://jsbin.com/tugupiwuqo/1/
The WebFont loader is there only to trigger some DOM activity in order to illustrate the slow performance in FF.
Actual results:
Very slow responses. Any changes in the DOM make Firefox lag, cripple transitions, and sometimes hang up the page for seconds. CPU usage is high.
Expected results:
Page should render smooth, like in other browsers.
I don't know if this helps, but one thing I noticed is that this becomes noticeable with a nest level of 7
Another issue is that printing fails with error in the Mac version, when nested flexboxes are present
Comment 3•11 years ago
|
||
Bug 1054010 fixed a category of issues like this. Could you try Firefox Developer Edition (which has that bug's fix) and see if this is any better for you there?
(In reply to pony from comment #2)
> Another issue is that printing fails with error in the Mac version, when
> nested flexboxes are present
(Yup, known limitation -- likely bug 939897.)
Updated•11 years ago
|
Component: Untriaged → Layout
Product: Firefox → Core
Comment 4•11 years ago
|
||
(Actually, if printing completely fails -- like nothing comes out of the printer [which I'm guessing based on your mention of an error message] -- then that's a different issue from bug 939897. Could you file a separate bug on that, and include a testcase that reproduces that issue for you? jsbin works, though a standalone .html testcase as an attachment on the bug is preferred. Thanks!)
Indeed the jsbin page does print, my development site doesn't (example: http://locationhost.com/mpgallery/flashpix). It shows "An error occurred while printing" when opening the PDF preview, and then a blank page.
But it seems that both issues are fixed in the Nightly version. Cheers!
Comment 6•11 years ago
|
||
Great! Resolving as WORKSFORME then. (i.e. the bug(s) have been fixed, though we don't know exactly what fixed it.)
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•