4 Коммитов

Автор	SHA1	Сообщение	Дата
Mark Banner	2bf9485071	Bug 1362947 - Upgrade eslint-plugin-html to 2.0.3 to pick up --fix support. r=jaws ... MozReview-Commit-ID: 5fVG7akPnGM --HG-- extra : rebase_source : e462e84bf8f2ffd893d1fd6b5ea14bbc093168dd	2017-05-08 10:29:47 +01:00
Sebastian Hengst	95a418ca5b	Backed out changeset e0f9c56c15f0 (bug 1362947) for linting failures, e.g. at accessible/tests/mochitest/jsat/doc_content_text.html:15. r=backout	2017-05-11 10:15:55 +02:00
Mark Banner	256aeb441c	Bug 1362947 - Upgrade eslint-plugin-html to 2.0.3 to pick up --fix support. r=jaws ... MozReview-Commit-ID: 5fVG7akPnGM --HG-- extra : rebase_source : f1b9eeb1b2048b551ee8c0a596e6395d0031cc4d	2017-05-08 10:29:47 +01:00
Patrick Brosset	a38e6ca6d7	Bug 1304685 - Show empty text nodes in markupview if they impact layout; r=jdescottes ... When the inspector actor walks the DOM in order to find nodes to be displayed in the inspector panel, it ignores text nodes that contain only whitespace characters (in order to avoid cluttering the panel with useless information). This commit changes this logic so that whitespace text nodes are only ignored when the node in fact has no layout at all (all text collapsed). Inside inline formatting contexts, whitespace text nodes may have layout and therefore push elements further apart. So seeing these nodes in the panel actually help debugging issues. MozReview-Commit-ID: GvNMsqsT3w6 --HG-- extra : rebase_source : 5c04eaf9e19e952d9f6ca267ef835e1846bc7f4a	2016-10-11 16:29:20 +02:00