зеркало из https://github.com/mozilla/gecko-dev.git
2feab69a17
This is what Chrome and Safari do. See https://webcompat.com/issues/20701#issuecomment-436054739 So for exmaple, if there are two viewport meta tags like this; <meta name="viewport" content="width=980"> <meta name="viewport" content="initial-scale=1,maximum-scale=1"> We will use "initial-scale=1,maximum-scale=1". Before this change we used to use merged "width=980,initial-scale=1,maximum-scale=1". Another example is to replace the content of a single viewport meta tag like this; <meta id="viewport" name="viewport" content="width=device-width, initial-scale=1"> what will happen when this tag is replaced by below; <meta id="viewport" name="viewport" content="width=1080"> We will use the replacing one (i.e. "width=1080"), before this change, we used to use merged "width=1080,initial-scale=1". As of this commit, we don't properly remove corresponding viewport meta data when a) viewport meta tag is detached from document and b) `name` attribute is changed from 'viewport'. These cases will be handled in subsequent commits. Note that we no longer store invididual viewport meta data in Document::mHeaderData so that nsIDOMWindowUtils.getDocumentMetadata doesn't work any more for the invididual viewport meta data, but there is no use cases for them other than two test cases which are removed in this commit. Differential Revision: https://phabricator.services.mozilla.com/D38922 --HG-- extra : moz-landing-system : lando |
||
---|---|---|
.. | ||
crashtests | ||
resources | ||
test | ||
CDATASection.cpp | ||
CDATASection.h | ||
ProcessingInstruction.cpp | ||
ProcessingInstruction.h | ||
XMLDocument.cpp | ||
XMLDocument.h | ||
XMLStylesheetProcessingInstruction.cpp | ||
XMLStylesheetProcessingInstruction.h | ||
htmlmathml-f.ent | ||
moz.build | ||
nsIXMLContentSink.h | ||
nsXMLContentSink.cpp | ||
nsXMLContentSink.h | ||
nsXMLElement.cpp | ||
nsXMLElement.h | ||
nsXMLFragmentContentSink.cpp | ||
nsXMLPrettyPrinter.cpp | ||
nsXMLPrettyPrinter.h |