Page MenuHomePhabricator

Browser search function to find work on a Wikidata item sometimes doesn't work
Open, Needs TriagePublic

Assigned To
None
Authored By
John_Cummings
Dec 13 2018, 12:39 PM
Referenced Files
F27716148: Screen Shot 2018-12-24 at 10.14.53.png
Dec 24 2018, 9:18 AM
F27716149: Screen Shot 2018-12-24 at 10.14.26.png
Dec 24 2018, 9:18 AM
F27716147: Screen Shot 2018-12-24 at 10.13.58.png
Dec 24 2018, 9:18 AM
F27535789: Screen Shot 2018-12-13 at 13.36.52.png
Dec 13 2018, 12:39 PM
F27535788: Screen Shot 2018-12-13 at 13.34.57.png
Dec 13 2018, 12:39 PM
Tokens
"Like" token, awarded by Jan_Dittrich.

Description

Some Wikidata items are really long and one way to find the property you're looking for is with Ctrl+F to bring up the browser word finder. Several times I've had an issue (with Safari, Firefox and Chrome) where the finder doesn't find the word on the page, even though the word exists on the page.

I think I've mainly seen it when searching for the first word in the name of a property e.g searching for the property 'model item' on an item page won't find 'model' (or searching for parts of that word), but will find 'item'

Screen Shot 2018-12-13 at 13.36.52.png (900×1 px, 140 KB)

Screen Shot 2018-12-13 at 13.34.57.png (900×1 px, 120 KB)

Event Timeline

John_Cummings renamed this task from Browser search function to find work in Wikidata item sometimes doesn't work to Browser search function to find work on a Wikidata item sometimes doesn't work .Dec 13 2018, 12:39 PM

Can you share links to 2 or 3 items where this happened for you?

@Lydia_Pintscher, sure, here are the items for city (Q515), planet (Q634) and library (Q7075), I've tried search for at least 10 different properties and I get the same behaviour

Screen Shot 2018-12-24 at 10.14.26.png (900×1 px, 117 KB)

Screen Shot 2018-12-24 at 10.14.53.png (900×1 px, 122 KB)

Screen Shot 2018-12-24 at 10.13.58.png (900×1 px, 126 KB)

Lydia_Pintscher added a subscriber: johl.

Hmm very weird. I tried it here and it works fine for me on those items. But I'm not using a Mac so maybe it's got to do something with it.
@johl or anyone else with a Mac can you please test?

Just FYI the version of Safari i'm using is Version 12.0.2 (13606.3.4.1.4) which I think is the latest version

I can confirm the same bug, tested on Safari Version 10 and 12.