Skip to content
New issue

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

Object (and embed) doesn't work being added as an element via HB #1344

Closed
denis-anisimov opened this issue Mar 9, 2017 · 8 comments
Closed

Comments

@denis-anisimov
Copy link
Contributor

Create an Element with "object" tag.
Set type to "image/svg+xml"
and set data attribute to some SVG image (e.g. use http://tecfa.unige.ch/guides/svg/ex/html5/green-circle.svg URL).
Add the element to the document,
Check it in EDGE.
Result: image is not shown.
For some reasons the svg URL is requested via HEAD http requested not GET.
It works fine in Chrome, FF and Safari.

It works also fine in EDGE if static markup is used.
May be something specific to "data" attribute.

@denis-anisimov
Copy link
Contributor Author

See hummingbird-demo#184

@Legioth
Copy link
Member

Legioth commented Mar 9, 2017

What happens if programmatically creating and adding a similar element from the developer console in Edge?

@denis-anisimov
Copy link
Contributor Author

Works fine.
It works in HB if element is created not via HB API.
See vaadin/flow-demo#206

@Legioth
Copy link
Member

Legioth commented Mar 9, 2017

Might this be yet another case where it matters whether parameters and attributes are set before or after the element has been attached to the DOM?

@denis-anisimov
Copy link
Contributor Author

You are right.
It doesn't work in EDGE via the console if element is added to the DOM before it's configured (i.e. create -> add -> set properties).
Works only when it's completely initialized and then added to the DOM.

@denis-anisimov
Copy link
Contributor Author

Can it be so that vaadin/flow-demo#203 is one more aspect of it ?
I.e. HTML import is added to the DOM before its URL is set......

@Legioth
Copy link
Member

Legioth commented Mar 9, 2017

Fully possible that it's the same problem with HTML imports as well.

Seems like we'd have to bump the priority of #481 that we put on hold to avoid doing anything premature before we've implemented the new template syntax...

@pleku
Copy link
Contributor

pleku commented Feb 26, 2020

This has been fixed by #481

@pleku pleku closed this as completed Feb 26, 2020
@pleku pleku modified the milestones: 1.0 Maintenance, 1.0.0.beta12 Feb 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants