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
The <wbr> is used only on one (REG) page at present, but it is unfortunate that Refinery converts it to xml-style, <wbr /> which browsers (Firefox, Chrome, Safari) delete as invalid or do not get to see. This means that users have to scroll to see the whole line: it should wrap.
Users see:
Whereas they should be able to see:
The wrapped version is fully responsive and does not require any scrolling.
Although one instance (and on a page for volunteers) might not seem important, it would be good to know whether we are able to change Refinery's behaviour towards <wbr> and other elements where no closing tag exists.
The text was updated successfully, but these errors were encountered:
@AlOneill is this something you are working on, or do you need input from anyone?
AlOneill
changed the title
Refinery converts a word-break to an invalid xml tag which browsers delete
Refinery converts a word-break to an invalid xml tag which either browsers delete or they never see
Apr 2, 2022
Interestingly, the preview window of my text editor (essentially a webkit rendering engine) respects the xml-style <wbr /> elements even though the Doctype is HTML5.
Is this another case of something happening between Refinery and the completed page as delivered to a browser? (Similar to what happens with ARIA attributes.)
The
<wbr>
is used only on one (REG) page at present, but it is unfortunate that Refinery converts it to xml-style,<wbr />
which browsers (Firefox, Chrome, Safari) delete as invalid or do not get to see. This means that users have to scroll to see the whole line: it should wrap.Users see:
Whereas they should be able to see:
The wrapped version is fully responsive and does not require any scrolling.
Although one instance (and on a page for volunteers) might not seem important, it would be good to know whether we are able to change Refinery's behaviour towards
<wbr>
and other elements where no closing tag exists.The text was updated successfully, but these errors were encountered: