Page MenuHomePhabricator

[partner] Change to Vector skin broke Apple's Dictionary.app
Closed, ResolvedPublic

Description

Users have found that the recent change in Wikipedia skin broke the parsing in Apple's Dictionary.app

http://www.corndogcomputers.com/tips/macos-dictionary-app-scroll-bug/
http://forums.macrumors.com/showthread.php?t=916518

Apple needs to fix this. It is not our problem. If you are experiencing this bug, please contact Apple and ask them to repair the problem, and preferably to make their application skin independent.

This problemreport exists solely, to inform you that you should contact Apple about the problem.


Version: 1.17.x
Severity: normal

Details

Reference
bz23602

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 11:07 PM
bzimport set Reference to bz23602.
bzimport added a subscriber: Unknown Object (MLST).

From reading up on it, it sounds like they've been screen scraping us for years and the Vector switchover killed them. Somebody should clue them in to the API ;-)

Silly Apple <3

Yeah, unfortunately those Dictionary.app deployments are out there everywhere and we have no clue how easy it would actually be to get Apple to push a fix on their end -- the scraping is done from JS that's built-in to the app, which is a default system component.

Worst case, maybe we can slip in some JS to hotpatch their JS that does the screen-scraping. ;)

As far as I know, dictionary.app has no unique useragent string. It uses the default Webkit UA. Perhaps there is something else in the headers, but it is a tad difficult to check.

User-agent wouldn't be feasible anyway; it fetches the regular URLs so would get cached pages.

Mac OS X Update 10.6.5:

  • resolve an issue with Wikipedia information not displaying correctly in Dictionary

Woohooo ! Will need to test myself, but sounds promising.

Confirmed to work.

Solution they chose: GET /w/index.php?title=pagename&useskin=monobook HTTP/1.1\r\n

ah well.

Apparently they've redone it to something else.. I've got someone poking someone else at Apple to find out what they've done now...

Ah, so this might be a temporary measure ?

One would hope they'd switched to using the API...