4 commits

Author	SHA1	Message	Date
Catrope	316fdab450	Actually use the doc parameter in toDomElements() ... It's been passed in for a while, but nothing ever used it. As we know some browsers don't like it when we create elements in the wrong document, and this ensures we always use the correct document for createElement(). Change-Id: Ia3d2fabe0516956105ad2b5625ed2f76c015c26e	2013-04-09 23:48:03 +00:00
Catrope	1645fe01e6	Be resilient against an unset hrefPrefix in MWCategoryMetaItem ... (or any unset attribute for that matter) Change-Id: I59364354c64fbce016090e17aa9683ec0a0fea9b	2013-04-08 21:44:59 -07:00
Catrope	b39576b433	Add MW-specific meta items for categories and language links ... Also rename MWMetaItem to MWAlienMetaItem, because that's what it really is. Change-Id: I70695bfa3b8449c936a63f7b2a248b90c49dcea1	2013-03-21 12:18:52 -07:00
Catrope	a835c03bc1	Change MetaNodes to MetaItems ... Rather than meta-things being special kinds of nodes, they are now a separate class of things (MetaItems) along with Nodes and Annotations. * Created a generic ve.dm.MetaItem that meta items inherit from. There will be actual instances of this class as well in the upcoming meta group code. * Renamed MetaNode to AlienMetaItem, MWMetaNode to MWMetaItem, 'metaBlock'/'metaInline' to 'alienMeta' * Created a MetaItemFactory, handle meta items in the ModelRegistry * Kill ve.dm.Node.static.isMeta, now obsolete ve.dm.Converter: * Pass in the MetaItemFactory * Look up data element types in the ModelRegistry rather than the NodeFactory, because they can be either nodes or meta items * Document createDataElement() and make explicit that modelClass can be either a node or a meta item * Handle meta items in getDataFromDom() * In getDomFromData(), check the MetaItemFactory as well as the NodeFactory Change-Id: I893709c6f3aa00f85c1b905b70f9f4e597bdeada	2013-03-14 23:35:50 -07:00