[WIP] Version 1.1 for Theme Feature (based on Sebastien Theme Code)

[Mercurial]

• I am converting the html.style CSS string into JSON string before saving into localStorage so it will be directly loadable by the ThemeManager via "variables" property

• I am manipulating SVG directly from React as Component to dynamically generate theme preview. (Which seems to be causing eslint to fail)

So we can argue that maybe we can replace SVG with pure HTML Elements to generate preview

• I also edited SVG code manually to be more responsive for aesthetic purposes

[Mercurial]

Hi Guys!
I have completed all the requested change by Sebastien except the DOM direct read access to get current customized styles.

Let me know what you think
Thanks
Clark

[SebastienGllmt]

I think you can clean this up by saving this as an svg file and then applying the color transformation using css style overrides in the Javascript. Maybe not a big deal though?

[Mercurial]

by the way, there is a specific test that fails because it expect to interact with a second theme but since we disabled it does fail.

should we disable that test?

Just a heads-up
Clark

[SebastienGllmt]

@Mercurial this is why I suggested you do "if not mainnet" instead of "if dev" that way the theme selection is still available during testing (this way the test passes)

[Mercurial]

firefox tests seems to fail, not sure why though