Last modified: 2014-11-18 21:05:06 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T75581, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 73581 - Parsoid doesn't support image blacklist.
Parsoid doesn't support image blacklist.
Status: NEW
Product: Parsoid
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Parsoid Team
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-18 21:05 UTC by C. Scott Ananian
Modified: 2014-11-18 21:05 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description C. Scott Ananian 2014-11-18 21:05:06 UTC
The mediawiki software prevents the display of inline images when the image source appears in the list in [[MediaWiki:Bad_image_list]].  See GlobalFunctions.php::wfIsBadImage in mediawiki/core.  There are existing parser tests for this, which use:

!!article
MediaWiki:bad image list
!!text
* [[File:Bad.jpg]] except [[Nasty page]]
!!endarticle

to set up the bad image list.

Parsoid doesn't support this, and the core imageinfo API does not include whether the image is Bad or not.  So if there is a bad image which is suppressed on the page in article view, it will suddenly appear when visual editor is started.

We probably need:
1. To patch mediawiki/core to add the result of wfIsBadImage to imageinfo (actually, if the image is bad, we need to return the set of exception page title, so we can't use wfIsBadImage directly).

2. To suppress the <img src> attribute if the queried image is bad for the current page context.  (The resource attributes can probably stay.)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links