| Quiddity | |
| Nov 13 2015, 1:06 AM |
| F41504585: Screenshot from 2023-11-14 12-08-31.png | |
| Nov 14 2023, 11:13 AM |
| F41504584: Screenshot from 2023-11-14 12-01-36.png | |
| Nov 14 2023, 11:13 AM |
| F41504587: Screenshot from 2023-11-14 12-08-19.png | |
| Nov 14 2023, 11:13 AM |
| F41504586: Screenshot from 2023-11-14 12-02-08.png | |
| Nov 14 2023, 11:13 AM |
In Phabricator's search, in Firefox (but not Chromium), if I type watc or watchl it will successfully autocomplete to "mediawiki-watchlist", but if I only type "watch" it doesn't match anything.
Confirmed in private window, as well as logged-in.
Very odd!
(No time to look upstream).
I've seen similar behavior in Google Chrome's omnibar (not at all related to this).
Very aggravating.
Probably because the JavaScript code in Phabricator treats an object as supporting arbitrary keys. watch is a non-standard reserved key in Object.prototype in Firefox's JavaScript engine.
The standard reserved keys are all in CamelCase such as toString, valueOf, hasOwnProperty. But Phabricator's script converts the value to lowercase before it searches, so those are fine.
Upstream bug! They need to use if hasOwnProperty.call( obj, key ) instead of if obj[key].
I think (?) I cannot reproduce this anymore in Firefox 119 as I see no difference in results (see screenshots below).
But maybe I perform the wrong steps? Would be great if someone could provide a full URL which exact "Search" this is about.
