- From: Greg Whitworth via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Mar 2017 22:33:19 +0000
- To: public-css-archive@w3.org
@fantasai @dbaron Ok here is my recipe I plan to run with: https://github.com/MicrosoftEdge/css-usage/blob/master/src/recipes/max-height-replaced-elems.js This does what I was saying in IRC that this will determine if a % is used on `max-height` and is on a replaced element with a `height` of `auto`. This does not go the further step of ensure that a parent somewhere up the tree has its `height` constrained to show this issue. This is more computationally intensive and will slow the crawl down, I think it would be good to cast our net wide and then scope it in. I can actually take the resulting URLs of the wide net and then scope the crawl to only the sites that have the potential problem and look for the actual issue. That said, even upon determining this we'll need to determine how many nodes we need to look up in the tree (if we limit it at all) and then also how we deem if the result would overflow causing the compat issue seen with `max-width`. We can figure this out after the crawl is complete. Please let me know ASAP if there is any concern with the recipe I linked to above. -- GitHub Notification of comment by gregwhitworth Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/765#issuecomment-283804421 using your GitHub account
Received on Thursday, 2 March 2017 22:33:26 UTC