-
Notifications
You must be signed in to change notification settings - Fork 1
1 Intro & Research
I need to understand CSS rendering edge cases in MediaExplorer. Search the codebase for:
-
Table rendering in RenderTreeBuilder.cs and RenderBox.cs — look for "table", "grid", "td", "th", "tr" handling. Report how tables are currently rendered and any known issues (look for TODO, FIXME, HACK comments related to tables).
-
CSS edge cases we've encountered — search for any TODO, FIXME, HACK, WORKAROUND, KNOWN in:
- RenderTreeBuilder.cs
- RenderBox.cs
- VirtualizingRenderer.cs
- DomBasicRenderer.cs
- CssLoader.cs
- CssComputed.cs
-
Search for any comments about "overflow", "text-overflow", "ellipsis", "white-space", "word-break", "word-wrap" to understand text rendering limitations.
Report:
- Table rendering approach and limitations
- All TODO/FIXME/HACK items found
- Text overflow/ellipsis handling status
- Any CSS properties that are parsed but not implemented Good, all six files located. Now let me search for all the requested patterns in parallel.
Now let me read the key sections of each file for deeper context on the table rendering, overflow handling, and text rendering.
Let me now read the table layout function in RenderBox.cs and search for more edge cases.
Let me also look at a few more key areas - the Temporarily Disabled display:none code, the VirtualizingRenderer overflow handling, and check for parsed-but-not-rendered CSS properties.
Let me check a few final pieces - how visibility, float, clear, and line-through are handled (or not) in the renderers.
Let me check the CssLoader.cs for what properties are parsed, and look at one final area - the "white-space" handling in VirtualizingRenderer to confirm the pre-wrap logic.