Re: [SVG2 CR] viewport-fill, viewport-fill-opacity

I might not have been clear in my last email.  I was referring to a
situation such as:

svg {
  background: red;
}

<svg>
  ... some elements here...
  <svg></svg>
</svg>

Currently, browsers will only apply the red background to the root <svg>.
If it gets changed to be valid on nested <svg> elements also, then it can
break existing SVGs by obscuring other elements.

Paul


On 22 September 2016 at 07:14, Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de>
wrote:

> Hello,
>
> presumable, if someone notes this, a red background is expected ;o)
> Maybe additionally the document contains a huge red circle or rectangle
> as first graphical element as fallback.
> But typically CSS stylesheets are not often used anyway for SVG documents.
>
> More problematic might be SVG fragments embedded in XHTML
> (this method is explicitly allowed in EPUB 2 and 3 - and works in several
> viewers better than embedding with img or object).
>
> But if one notes
> figure  * {background-color: red}
> one might mean other content than an SVG within the figure.
> If suddenly the background appears for the SVG, this could be a surprise.
> On the other hand most EPUBs are generated anyway by relatively simple
> programs, either not using SVG at all or in case of calibre only in a
> surprising way to embed a raster image within the cover page, using only
> scalability of SVG.
>
> Olaf
>
>
> Paul LeBeau:
> > I wonder how many sites out there might have a CSS rule such as:
> >
> >     svg {
> >         background-color: red;
> >     }
> >
> > If backgrounds suddenly start applying to nested elements (in order to
> > replace viewport-fill), would that potentially break existing sites?
> >
> > Paul
> >
>
>
>