3 Commits

Author	SHA1	Message	Date
Ojan Vafai	a267c39c01	Remove the concept of staticly positioned absolutes. ... On the web, if you set position:absolute, but not top/right/bottom/left, then the absolute goes where it would have gone if it wasn't positioned. The use-cases for this are slim and it introduces a lot of complexity to the engine. Also changes behavior in the presence of direction:rtl. On the web, direction:rtl and top/left:auto would sometimes set right:0. Instead we always position at 0,0 if the opposing values are auto. This removes the code for this positioning and allows simplifying a bunch of dirty bit handling code since we don't need to setNeedsLayout if lines move around or wrap differently. The test cases did change their output, but the new positioning all looks correct to me. Review URL: https://codereview.chromium.org/944073006	2015-02-20 20:26:59 -08:00
Ojan Vafai	0c37a8a322	Fix painting of position:absolute inside display: paragraphs. ... We only need to walk the immediate children of the paragraph. The other inline children of the paragraph will get paint called on them and they will then appropriately add the self painting layers to the array inside their paint calls. R=abarth@chromium.org Review URL: https://codereview.chromium.org/945223002	2015-02-20 20:24:57 -08:00
Ojan Vafai	ee7448297c	Add render tree dump and pixel tests for statically placed position:absolute. ... This exposes a bug that we position and size position:absolute correctly inside paragraphs, but we fail to paint them. R=abarth@chromium.org Review URL: https://codereview.chromium.org/943113003	2015-02-20 18:20:23 -08:00