+ bettes@ for guidance.

Separated font size issues with side nav to  Issue 778074 .

Downgrading this to a P3. Explaining rationale below:

Drastically changing the font size and expecting the UI to look descent/usable is a bit of a stretch. It is a reasonable expectation for an article/document type of page, but it seems unreasonable for an app-like interface, like MD Extension's card layout. As another data point, Gmail (which I would classify as an "app" and not as a article/document), also looks poor on a very large font size.

Unless we are willing to also modify the dimensions of the cards/toolbar when the font changes, the result will not be that pleasing anyway. At the same time, changing the dimensions of cards/toolbar sounds very similar to what zoom-ing already does, so unclear whether that is worth implementing either.

Thinking more about this, I am skeptical on why our WebUI pages respect the font-size setting at all. Perhaps that setting should be ignored by WebUI pages (and should only applied to remote Web content).

Having said that, if there are cases where with a reasonable font size poor layout is observed, maybe with a language other than English  language, or when an even slightly larger font size is used (like when using "large"/"very large" presets from chrome://settings/appearance), we could increase priority for those cases.

Un-assigning myself for now. See #8 for a more detailed reasoning, about why I don't think the issue described here is worth investing much time.