Bug 1853255 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

STR: 

1. `data:text/html,<style>ul,li { display:inline; list-style-type: none;list-style-position:inside;margin:0;padding:0; }</style><div style="background:green; max-width: 400px;">List of information: <ul><li>item one</li> | <li>item two</li> | <li>item three</li> | <li>item four</li> | <li>item five</li></ul></div>`
2. Using VO, step into the list and navigate by item

Expected:
VO cursor bounds each item of the list tightly

Actual:
VO cursor is offset by the length of "List of information: " in the X direction. Ee construct the parent bounding box by drawing a tightly fitting rectangle over all child content. This makes the bounding box's origin X = min(x coord of each child's origin), Y= min(y coord of each child's origin). We then layout each child relative to that point. 

This is broken because the actual DOM origin of the list is _not_ computed with min(X, Y of children), it is the point at which the list begins, on the line it begins in (ie. not across lines). 

I think the fix here is to compute the bounding box later and/or add any offsets we make to the original origin into the child origins.
STR: 

1. `data:text/html,<style>ul,li { display:inline; list-style-type: none;list-style-position:inside;margin:0;padding:0; }</style><div style="background:green; max-width: 400px;">List of information: <ul><li>item one</li> | <li>item two</li> | <li>item three</li> | <li>item four</li> | <li>item five</li></ul></div>`
2. Using VO, step into the list and navigate by item

Expected:
VO cursor bounds each item of the list tightly

Actual:
VO cursor is offset by the length of "List of information: " in the X direction. We construct the parent bounding box by drawing a tightly fitting rectangle over all child content. This makes the bounding box's origin X = min(x coord of each child's origin), Y= min(y coord of each child's origin). We then layout each child relative to that point. 

This is broken because the actual DOM origin of the list is _not_ computed with min(X, Y of children), it is the point at which the list begins, on the line it begins in (ie. not across lines). 

I think the fix here is to compute the bounding box later and/or add any offsets we make to the original origin into the child origins.

Back to Bug 1853255 Comment 0