Barry Hughes

Changing team, as this seems to have its origin in this recent change (for which Proton doesn't have the same amount of context): https://github.com/woocommerce/woocommerce/pull/43872

Please feel free to re-request review once any feedback is addressed and you are happy for us to take another look :-)

A note that this doesn't seem to be reflected in the [current CLDR data](https://github.com/unicode-org/cldr/blob/release-44-1/common/subdivisions/en.xml#L1174-L1221), which is the standard we follow and generally tell contributors we need to adhere to.

> Hey @barryhughes I tried to figure out the contribution process to CLDR and it's confusing at best, and undoable at worse. Very belated follow-up here. Some changes like this...

Thanks for reporting this, though it can be really helpful to us if you follow the bug report template. Some information we'd ideally like to see: > **WordPress Environment** >...

Related: https://wordpress.org/support/topic/woocommerce-email-header-too-large/

Thanks—I see something similar on (some) Gmail/Android combinations, depending on the device and screen size. We're testing some tweaks, including the one you suggested, however striking the correct balance across...

```html ``` @CIPURTA I'm a little unsure where you are suggesting we apply that. Regarding a previous suggestion: > 100% width for the table, it was a fixed width of...

Unassigning, as this is not actively being worked upon.

@coreymckrill this isn't ready for full review yet, but I still wanted to get a provisional review for some thoughts on the basic concept I'm trying out with `Types::ensure_is_type_or_wp_error`.