- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Jul 2021 12:42:50 +0000
- To: public-css-archive@w3.org
> I assume the "multiple annotations" in "...multiple annotations spanning the same number" means over various rows? yes. Now clarified in the spec. To better explain what the "problem" with 3.1.1 is, let me start with something that isn't a problem: ``` [a11] [ a1-23 ] [b-1] [b-2] [b-3] ``` If the text in annotation a1-23 is wider than the sum of b-2 and b-3, the excess is distributed equally among the spanned columns. Same thing for a2-12 with b-1 and b-2 here: ``` [ a2-12 ] [a23] [b-1] [b-2] [b-3] ``` However if you have a multi-level annotation like this, we have a (small) problem: ``` [ a2-12 ] [a23] [a11] [ a1-23 ] [b-1] [b-2] [b-3] ``` In this case if a1-23 is wider than the sum of b-2 and b-3 AND a2-12 is wider than the sum of b-1 and b-2, depending on how you go about doing it (distribute a1-23 first, distribute a2-12 first, somehow combine), the result may be different. All the potential results will be correct and keep things sensibly aligned, but the specification doesn't (at the moment) say how to resolve this ambiguity. For instance, let's say that the content of all bases and annotations are 10px wide, except a1-23 which is 40px, and a2-12 which is 30px. If you distribute a1-23 first, you make the b-2 and b-3 columns 20px wide each, and then since a2-12's 30px do fit within over b-1 + b-2 (10px+20px=30px), you stop there. The columns end up being 10px, 20px, 20px. However, If you distribute a2-12 first, you make the b-1 and b-2 columns 15px wide each, and then since a1-23's 40px do not fit within over b-2 + b-3 (15px+10px=25px), you need to distribute the 40px-25px=15px equally between these two columns, making b2=15+15/2=22.5 and b3=10+15/2=17.5. The columns end up being 15px, 22.5px, 17.5px. It's unlikely to be a real issue, but depending on how specific you are about the result you'd like to see, you might notice. This is a solvable problem, but leaving this undefined for now was a deliberate choice: given the absence both of a markup language where this case can occur, and of known use-cases documenting that this matters, this didn't seem worth diving into. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6432#issuecomment-879858050 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 14 July 2021 12:42:51 UTC