Editing code in dev tools has no effect

[smlombardi]

I sometimes need to add a class to the body or html tag or similar to simulate a different condition, like a Modernizr test or angular ng-class, or some other device-related thing that can't be done with a media query.

To do this in Chrome, I open the dev tools and manually edit the classes in the body tag. The page now looks like it should. When I open re-view's device wall, it reloads the page and my edits are gone (as expected with a reload). But even if I open the dev tools and re-do my temporary edits, nothing happens.

It would be nice to have some way to affect the code via dev tools for the device wall.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/31183705-editing-code-in-dev-tools-has-no-effect?utm_campaign=plugin&utm_content=tracker%2F3374384&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F3374384&utm_medium=issues&utm_source=github).

[sergeche]

Re:view loads a fresh copy of document in each view so you have to make changes like that in view iframes. I’m working on sync CSS update between views right now (as a part of LiveStyle integration), but I don’t know if I can do something similar with HTML

[smlombardi]

I know when you set up a custom device you can set a user agent. Perhaps you could at some point add the ability to inject classes to html or body tags for a custom device? Only if that makes sense, of course. :-)

[sergeche]

If these classes are based device features (width, resolution etc.) it’s possible to override them in Device Wall mode. I just need a few examples of these features. Option for adding custom classes for Device Wall pages looks a bit hacky

[brummm]

LiveStyle working with re:view would be awesome.