You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 19, 2024. It is now read-only.
First of all: is this the desired behaviour? If so, what is the rationale? If not, why not remove absolute positioning from child elements?
What I am trying to produce is a layout in which iron-pages children will remain in the normal css position flow. I can achieve that using Developer Tools inspector (disabling position: absolute from the rendered children), or programatically setting a custom-style rule that targets test-page and sets position: static, but I am not sure if that might break something down the road.
I have prepared a jsbin to illustrate this: http://jsbin.com/novemeqaro/edit?html,output. Try commenting out the position property from custom-style and resize window so that iron-pages yellow content overlaps the blue page footer.
At least from this example, there is no penalty to the layout leaving the position attribute to static.
Thanks
The text was updated successfully, but these errors were encountered:
First of all: is this the desired behaviour? If so, what is the rationale? If not, why not remove absolute positioning from child elements?
What I am trying to produce is a layout in which
iron-pages
children will remain in the normal css position flow. I can achieve that using Developer Tools inspector (disablingposition: absolute
from the rendered children), or programatically setting acustom-style
rule that targetstest-page
and setsposition: static
, but I am not sure if that might break something down the road.I have prepared a jsbin to illustrate this: http://jsbin.com/novemeqaro/edit?html,output. Try commenting out the
position
property fromcustom-style
and resize window so thatiron-pages
yellow content overlaps the blue page footer.At least from this example, there is no penalty to the layout leaving the position attribute to
static
.Thanks
The text was updated successfully, but these errors were encountered: