@Jdlrobson: +1

Change 202760 had a related patch set uploaded (by Jdlrobson):
Border box no longer default

https://gerrit.wikimedia.org/r/202760

Change 202760 merged by jenkins-bot:
Border box no longer default

https://gerrit.wikimedia.org/r/202760

So while the latest patch fixes VE, I'd still like to switch all views over to not use the border-box * selector. Any components of MF that may get shared between read mode & VE (for example, the toolbar) could render differently. Also future components that might be embedded in the regular view, but which aren't owned by MF may have the same problem as VE.

Change 218608 had a related patch set uploaded (by Esanders):
Never apply border-box to 'body' (i.e. for a 'Skin')

https://gerrit.wikimedia.org/r/218608

Change 218608 merged by jenkins-bot:
Never apply border-box to 'body' (i.e. for a 'Skin')

https://gerrit.wikimedia.org/r/218608

• https://gerrit.wikimedia.org/r/218608 (branch master): WMF-deploy-2015-06-16_(1.26wmf10)

Note: The latest fix has introduced some visual regressions which have made it out on to 1.26wmf10. See T102868: Big logout icon we need to decide whether to revert this or work on top of it some fixes (please don't rush changes to the box-sizing defaults in future without vigorous testing across the whole of the mobile site)

Once the patch is reverted, I'll restore it and we'll review/test it a bit more vigorously second time round to fix up the remaining issues with content inside the skin.

Change 223176 had a related patch set uploaded (by Jdlrobson):
Skin itself should not be border box

https://gerrit.wikimedia.org/r/223176

I'm a bit lost here -- and totally admit that could just be my lack of understanding re: how LESS "works" or something so I apologize in advance if this is rather 'obvious' to you coder types -- but what exactly is changed by r223176 of July 6th if the .view-border-box class is still present in the BODY element and still defined to cascade down to any & all of it's decendants &/or children elements (.view-border-box *, .view-border-box)?

Sure - I can grasp the fact the class name was added to certain elements - I'm just not sure what difference that makes if the BODY element's cascade is still in place (or is that stopped by the added bits to Skin.js?).

I have to ask because when halting that "body cascade" was the aim two or three weeks ago, it had to be reverted in r219877 to recover from all the "deviations" applying it had exposed in process.

Thanks for your time at any rate.

@GOIII: 219877 was reverted because it caused a handful of regressions.

As of 223176, the view-border-box class won't be present on the body element, which is the result of [the change to the Skin class](https://gerrit.wikimedia.org/r/#/c/223176/1/resources/mobile.startup/Skin.js) as you pointed out. So the major difference between the initial and current patches is that the latter also addresses the regressions caused by the change.

The file that I was trying to share on 223176 was

Thanks for the clarification, phuedx.

Still think this is a bad idea; fixed skin design and format should use one setting (imho: border-box) and the branch/container dealing with user initiated content, templates and the like should also have one setting (in this case; content-box).

Eliminating the attribute & allowing the default (content-box) to reign simply by attribute omission doesn't seem to be the optimal way forward.

Change 223176 merged by jenkins-bot:
Skin itself should not be border box

https://gerrit.wikimedia.org/r/223176

This is merged. @Esanders any follow ups required. Does VE look good to you? (All looks well to me)

@Jdforrester-WMF set Story Points to 40.

Wat?

sounds pretty accurate, but hindsight is 20/20 ;)