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'm using React in a Chrome App and it seems like it doesn't support the tag. I know this is a pretty specialized scenario so I don't know if it belongs in core, but is there some way I can manually add support for that tag, at least for a single project?
You could easily create and attach it yourself during componentDidMount, it's obviously not the same thing, but I imagine that it will work just as well for you and you don't have to wait for another release for the fix (which might not happen "soon").
Sounds like a plan @syranide. I'll use the componentDidMount method for now. You're welcome to close this issue if you want, but I figured I'd leave it open in case you do choose to add <webview> as a supported tag in a future release.
Well, I said I wouldn't support it because it's not real html, so I guess I need to follow through. We no longer use the whitelist for dom components when going through React.createElement in 0.12 so if you wanted to use that directly you could and it might work (no guarantees). But we do still use the whitelist when transforming JSX, at least for now to provide a clean upgrade path to the future.
Activity
syranide commentedon Aug 28, 2014
You could easily create and attach it yourself during
componentDidMount
, it's obviously not the same thing, but I imagine that it will work just as well for you and you don't have to wait for another release for the fix (which might not happen "soon").jRiest commentedon Aug 29, 2014
Sounds like a plan @syranide. I'll use the
componentDidMount
method for now. You're welcome to close this issue if you want, but I figured I'd leave it open in case you do choose to add<webview>
as a supported tag in a future release.zpao commentedon Oct 29, 2014
Well, I said I wouldn't support it because it's not real html, so I guess I need to follow through. We no longer use the whitelist for dom components when going through
React.createElement
in 0.12 so if you wanted to use that directly you could and it might work (no guarantees). But we do still use the whitelist when transforming JSX, at least for now to provide a clean upgrade path to the future.