GNOME Bugzilla – Bug 165811
Spaces don't work in type-ahead find
Last modified: 2009-02-27 13:00:28 UTC
This bug has been opened here: https://bugzilla.ubuntu.com/6013 "Note that this isn't just a highlighting problem, it's a problem with actually finding strings with spaces in them in the first place. Eg: 1. Go to http://www.ubuntu.com/ 2. Type / 3. Type "ubuntu linux" 4. Observe that although there are exact matches for "ubuntu linux" (which are found correctly with the Ctrl+f find dialog), the highlighted text stays on the first "ubuntu" match on the page, rather than finding "ubuntu linux" at all."
Confirming. It works in mozilla trunk (1.8b-ish) and its TestGtkEmbed, but not in Epiphany compiled against it. http://lxr.mozilla.org/seamonkey/source/extensions/typeaheadfind/src/nsTypeAheadFind.cpp 688 // ---------- PreventDefault check --------------- 689 // If a web page wants to use printable character keys, 690 // they have to use evt.preventDefault() after they get the key 691 nsCOMPtr<nsIDOMNSUIEvent> uiEvent(do_QueryInterface(aEvent)); 692 PRBool preventDefault; 693 uiEvent->GetPreventDefault(&preventDefault); 694 if (preventDefault) { 695 return NS_OK; 696 } Spaces don't pass this check, i.e. someone is calling PreventDefault() on those keypresses. But Epiphany has no keypress handler (nor keydown)!
Created attachment 36765 [details] gdb log
+ Trace 55123
Here's the handler that's calling PreventDefault()
Doesn't happen in galeon compiled against mozilla trunk. Still happens without any epiphany extensions installed.
This seems to be caused by the change from bug 141963: when epiphany starts with accessibility.typeaheadfind.autostart set to 'true' typeaheadfind finds spaces; when I set it to 'false' or if I start epiphany with it being 'false', typeaheadfind doesn't find spaces.
Fixed in cvs. Someone should forward this bug to b.m.o.
Is it possible to backport the fix to the 1.4 series?
The patch from bug 141963 was never applied to gnome-2-8 branch, so this bug shouldn't occur there.
This doesn't occur in Epiphany 2.14 (at least for me), would it be ok to close it?
No, see comment 5.
Christian, is a mozilla bug still needed? I will file one if that's all that's keeping this bug open.
chpe, ping?
The thing is that explaining what exactly the bug to file is about would require approx. the same energy as filing it myself :)
This works in Epiphany/WebKit. Closing.