View Single Post
Old 07-04-2023, 03:09 PM   #57
nabsltd
Fanatic
nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.
 
Posts: 528
Karma: 9529956
Join Date: Aug 2013
Location: Hamden, CT
Device: Kindle Paperwhite (11th gen), Scribe, Kindle 4 Touch
Quote:
Originally Posted by Turtle91 View Post
Using % does NOT work all the time. I do NOT use % because it was creating a problem that was solved when I used vw/vh.
This is likely because % and vh/vw do not mean the same thing. % means a percentage of the immediately enclosing block element's bounding box. vh/vw is supposed to be a percentage of the whole screen, although some renderers/devices might ignore the minimum outer margin that the device forces.

Full-page images (like covers) using SVG don't have a lot of extra CSS blocks around them, and what your code shows should have 0 margin from the edge of the screen, but there can be CSS in the user-agent-stylesheet that is taking effect.

It's tough to know if you can't inspect the element and figure out what is getting applied.
nabsltd is offline   Reply With Quote