Don't remove the actual stylesheet nodes when viewing houston

[matteodem]

At the moment we remove all other stylesheets that are present to the current meteor app and when switching (without completely refreshing the app) sites, they'd have no styling applied anymore after viewing Houston.

I'd strongly suggest we don't do that anymore, since we also prevent people from overriding the admin styles and it's a hack.

[AlexeyMK]

Happily - what do you think would be a better solution? The current one was
one of those "least-bad-idea" type things.

On Sun, May 11, 2014 at 11:02 AM, matteodem notifications@github.comwrote:

At the moment we remove all other stylesheets that are present to the
current meteor app and when switching (without completely refreshing the
app) sites, they'd have no styling applied anymore after viewing Houston.

I'd strongly suggest we don't do that anymore, since we also prevent
people from overriding the admin styles and it's a hack.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/172
.

[matteodem]

• Not removing stylesheets at all (since the styles are prefixed with .houston, if I remember right)
• Corrupting the stylesheet links and replacing them again after leaving the houston ui (also hacky)

[AlexeyMK]

Cc @gterrono

I think the reason we remove user defined stylesheets is when they style
top-level things like "form" or "input" - in Houston's case, this is a bad
idea, but blaming the user is no great solution.

I think manually putting the stylesheets back in is probably a workable
idea - but so is (and maybe this is easier) patching ironrouter so that any
link to a non-houston resource requires a hard reload (using
window.location = ...)

Sounds like a fun (though somewhat hacky) thing to play with.
On May 12, 2014 11:58 PM, "matteodem" notifications@github.com wrote:

• Not removing stylesheets at all (since the styles are prefixed with
  .houston, if I remember right)
• Corrupting the stylesheet links and replacing them again after
  leaving the houston ui (also hacky)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/172#issuecomment-42923185
.

[gterrono]

Yeah, we need to remove the css because it interferes with houston. I think the best option is to add all the stylesheets back when we go to a non houston page, although that's just adding a hacky solution onto a hacky solution.