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
With Javascript disabled, HTML tooltip support is obviously non-functional. However, the Elements Demo page gives no indication as to what will happen if both an HTML and traditional tooltip are supplied.
Will it cause things to break horribly or will HTML KickStart remove the textual tooltip when it detects an HTML one, allowing the textual tooltip to be used as an equivalent to <noscript> and <noframes>. (And, if it does break, that should probably be considered a bug too)
I've got ready access to server-side libraries which attempt to generate pleasing plaintext from input HTML, so it's not as if it's an onerous thing to do even if I'm working with user-provided data.
The text was updated successfully, but these errors were encountered:
With Javascript disabled, HTML tooltip support is obviously non-functional. However, the Elements Demo page gives no indication as to what will happen if both an HTML and traditional tooltip are supplied.
Will it cause things to break horribly or will HTML KickStart remove the textual tooltip when it detects an HTML one, allowing the textual tooltip to be used as an equivalent to
<noscript>
and<noframes>
. (And, if it does break, that should probably be considered a bug too)I've got ready access to server-side libraries which attempt to generate pleasing plaintext from input HTML, so it's not as if it's an onerous thing to do even if I'm working with user-provided data.
The text was updated successfully, but these errors were encountered: