We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSS.elementSources
Can you please clarify if you plan to drop CSS.elementSources? or even image()?
image()
CSS.elementSources was hidden before #3572, which defined it with any as its type.
any
partial namespace CSS { [SameObject] readonly attribute any elementSources; };
In #428, fixed by the above PR:
that spec version is way out of date and needs to get some stuff dropped.
If it should not be dropped, is there a reason to not define it as a maplike?
maplike
EXAMPLE 13 <script> var bg = document.createElement('canvas'); CSS.elementSources.set('fancy', bg); </script>
EXAMPLE 13
<script> var bg = document.createElement('canvas'); CSS.elementSources.set('fancy', bg); </script>
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Can you please clarify if you plan to drop
CSS.elementSources
? or evenimage()
?CSS.elementSources
was hidden before #3572, which defined it withany
as its type.In #428, fixed by the above PR:
If it should not be dropped, is there a reason to not define it as a
maplike
?The text was updated successfully, but these errors were encountered: