Last modified: 2014-05-15 19:12:40 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 T63969, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 61969 - VisualEditor: Deal with universal types like mw:Error, mw:ExpandedAttrs, mw:Placeholder
VisualEditor: Deal with universal types like mw:Error, mw:ExpandedAttrs, mw:P...
Status: ASSIGNED
Product: VisualEditor
Classification: Unclassified
Data Model (Other open bugs)
unspecified
All All
: High major
: ---
Assigned To: Ed Sanders
:
Depends on:
Blocks: 50788 63941 65362
  Show dependency treegraph
 
Reported: 2014-02-26 23:48 UTC by Roan Kattouw
Modified: 2014-05-15 19:12 UTC (History)
5 users (show)

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


Attachments

Description Roan Kattouw 2014-02-26 23:48:17 UTC
Some types like mw:ExpandedAttrs are universal, meaning they can apply to any element and their presence shouldn't be taken into account when figuring out which node handler to invoke. The node handlers themselves probably do need to make decisions based on their presence, but that's fine, they can do that already.

For now the approach I'm considering is to add the concept of a universal RDFa type, which will be ignored by ve.dm.ModelRegistry#matchElement for all purposes (including the "if not all mw: types are matched it's not a match" logic and all of that). mw:ExpandedAttrs and mw:Error (the latter would be introduced by bug 50788) would be universal types. mw:Placeholder wouldn't be one, because it needs to trigger alienation.

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


Navigation
Links