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
Special handling for boolean attributes like <div contenteditable></div>, where contenteditable should be coded as contenteditable=true, should be documented in the yew docs
The text was updated successfully, but these errors were encountered:
Why can't <div contenteditable></div> be handled as is by the parser? If it's possible, it would make it more similar to vanilla html and could prevent a few headaches.
Why can't <div contenteditable></div> be handled as is by the parser? If it's possible, it would make it more similar to vanilla html and could prevent a few headaches.
I think this is still mainly a documentation issue. Sure, we could add that syntax for convenience but then I fear users will start asking how to disable a boolean attribute instead. Enforcing a strict key=value syntax is also easier to handle for components, which can't easily support boolean attributes like that.
If you want to add the special handling for this though then by all means, go ahead.
Special handling for boolean attributes like
<div contenteditable></div>
, wherecontenteditable
should be coded ascontenteditable=true
, should be documented in the yew docsThe text was updated successfully, but these errors were encountered: