Re: [csswg-drafts] [css-ui] Control whether an element is findable/searchable (Ctrl+F) (#3460)

Thank you for discussing the issue.

To quickly respond to an idea in the log: while I don't have great difficulty accepting the "probably should have used ruby" argument, and per the spec the semantics of ruby are left very open, it may be worth noting a few things:

1. Ruby is indeed already being used in the application that this use-case is from, but for marking up phonetic annotations (it's not shown in the first example/jsfiddle, but shown in the second example/jsfiddle without the numeric annotations). I know from other experimentation that nesting ruby annotations, esp. with unequal bases, is quite difficult to make work.
2. Some annotations are intended to go "between" two words rather than be associated with any individual word. Imagine in the first example/jsfiddle adding another tick at the very end of the sentence with the text "<samp>**100%** 5</samp>": what word would this annotation attach to?
3. The tree model of HTML/XML/CSS makes it quite tricky to annotate a span of markup arbitrarily (e.g. highlight a range of text and add a comment; OOXML e.g. uses milestone elements). Any existing method (ruby, positioned spans, tables) of interlinear annotation runs into issues of findability, copyability, and selectability anyway, not to mention line-wrapping or overlapping.
4. There is another person's application that does use ruby for the word-associated annotations: [example A](https://quizbowlstats.com/buzzpoints/set/2024-acf-regionals/tossup/ottoman-empire). Compare to my [example B](https://every.buzz/jank/question_sets/2019-acf-regionals/editions/2019-01-26/tossups/ottoman-empire.html) (note that the ruby tags with phonetic annotations are hidden by CSS for the purpose of this application).

Hope this context helps a bit to understand one of my motivating use cases.

-- 
GitHub Notification of comment by hftf
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3460#issuecomment-1945284587 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 15 February 2024 02:53:36 UTC