Overview Description: Selection does not appear to work fully when attempting to select content that is part of the anonymous content of an XBL binding. (This is for future consideration, as there is no UI requirement for NS6 to have this work, as far as I know). Steps to Reproduce: 1) Load http://www.shadowland.org/xbl/test4/test.html 2) Use the left mouse to select the text "A table with a single cell". 3) Now right click to get a context menu over the selection, and then do a right click elsewhere in the page. Actual Results: at 2) the selected text is not highlighted at 3) portions in the lower half of the line-height are shown in highlight (on windows); no change on mac or linux Expected Results: at 2) the selected text is highlighted at 3) the selected text is highlighted Reproducibility: always Build Date & Platform Bug Found: 20000908nn win32/mac/linux Additional Information: from n.p.m.xpfe Not sure if it's been filed yet, but selection seems to be confused when it comes to anonymous content. Probably a bug for mjudge. dave pUnk wrote: > Ok, the #4 testcase. > > It looks like the green table cell has all kinds of strange selection > garbage. Try to select the text (by dragging the mouse). Now press RMB > (context-menu). A part of the text in the cell will be selected, but > only the lower half of the characters (very weird looking).
Summary: Selection problems with XBL anonymous content. → Selection problems with XBL anonymous content.
John, we think so alike it's scary. I also just read this post. I also was just about to file a bug. See also bug 48346, a similar problem I reported also concerning the XBL testcases and anonymous content.
I'm seeing some really wonky selection stuff in an XBL article on Netscape DevEdge (http://developer.netscape.com/evangelism/docs/articles/xbl/). Am I seeing this bug, or is this something different? Using 2001101808 on SuSE Linux.
changing selection qa to tpreston.
QA Contact: blaker → tpreston
Assignee: mjudge → nobody
QA Contact: tpreston → selection
You need to log in before you can comment on or make changes to this bug.