My tab renders as: " > ".
I still consider it whitespace.
replyWhat turns into whitespace due to rendering? Just because my font lacks that symbol doesn't mean it is whitespace.
One example is a field that clips its contents to contain zalgo, but inadvertantly to the point where some glyphs can render completely out of bounds. Sometimes the clipping is so egregious that even descenders of normal letters like 'g' get cut off. (This is more common than you'd think.)
replyI get the desire to filter that out, not sure whether I'd classify it as whitespace though.
replyTrue, rendering out of bounds doesn't make something actually whitespace, it just means it could look like whitespace. Though, consider the case where someone is looking to detect if a character is whitespace, when what they actually want is to detect if it could look like whitespace. That's where context comes into play. Irrelevant if it's not about the looks, but potentially relevant if it is, hence why I figured I'd leave a quick comment about it here.
replyI don't think you can "just render it" to figure out it's whitespace?
replyAs the section "What is whitespace, anyway?" points out, if you render an OGHAM SPACE MARK in a font with a stemline you'll get a visible horizontal line.