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
I would like to propose the following, which would allow developers to easily identify overflow issues, and correctly deal with them,
to ensure their pages render correctly.
With the new render modes as suggested and proposed in #10403
The following properties would make mobile development so much better.
The names of the properties could be shortened.
.classname[device-overflow-inflated-width]::before {
display:block; // force the item onto a new rendering line.
}
}
@Loirooriol Yes, I would want to apply styles to elements that overflow the viewport, to selectively re-align or change the layout, such that they fall into the viewport and in the case of this proposal, prevent the viewport from being blowing up and limit that for mobiles to a factor and zoom, such pages have less issues rendering on mobile and it then just work, see #10403
I am using an attribute selector to inspect the property, but using a pseudo-class can work as well, anything that can inspect or make logical decisions in all places required based on an internal dom boolean variable.
I would say, that depends on how you structure the code and pre-evaluation of a render buffer of line render elements, before flushing them to pixels, which would allow injection of before items, like currently happens. You can also limit the recursive iteration to a single overflow functional evaluation, which probably would be good for fixing and sorting most website pages out.
I am pretty sure it would be possible.
Hi,
I would like to propose the following, which would allow developers to easily identify overflow issues, and correctly deal with them,
to ensure their pages render correctly.
With the new render modes as suggested and proposed in #10403
The following properties would make mobile development so much better.
The names of the properties could be shortened.
The text was updated successfully, but these errors were encountered: