User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20060308 Firefox/22.214.171.124 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20060308 Firefox/188.8.131.52 At koders.com, when you view source, on the left side there are line numbers. Try searching for '11' on a source page (say the link above). When you get to a line number that ends with '1', and on the next line starts with '1', a match is made. However, it really shouldn't be, because there is more text on the right hand side. Looking at the page source, the problem seems to be that Firefox reads the table code as one (just as it's in the page source); for example, the line-showing code looks like this: <code><a href="#L111" name="L111">111</a><br/><a href="#L112" name="L112">112</a><br/>...</code> So, of course, to FF, this looks like that's how the page is set up... with numbers showing continually from left to right (though there are br's there). However, it's one per line. Reproducible: Always
The numbers down the left side are just one big div, with <pre> and <br/>s seperating the number. I guess this is the same as bug 139225?
(this component sucks, but apparently it's where find bugs go for lack of it's own component)
Mozilla/5.0 (X11; U; Linux i686; rv:1.9b5pre) Gecko/2008032501 SeaMonkey/2.0a1pre Behavior exist, but its logical for me, find should find in text, not in metadata. Resolving as WFW, reopen if not agree