# Targeting Ember CSS IDs results in weird behavior

**URL:** <https://meta.discourse.org/t/targeting-ember-css-ids-results-in-weird-behavior/60628>\
**Category:** Product Support\
**Created:** [April 8, 2017, 4:04am UTC](https://meta.discourse.org/t/targeting-ember-css-ids-results-in-weird-behavior/60628 "2017-04-08T04:04:27Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![cpradio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cpradio/32/4970_2.png) [@cpradio](https://meta.discourse.org/u/cpradio)\
**Post date:** [April 8, 2017, 11:50am UTC](https://meta.discourse.org/t/targeting-ember-css-ids-results-in-weird-behavior/60628/2 "2017-04-08T11:50:58Z")

</div>

You need to delete this CSS rule

```plaintext
body.category-deformers-techsupport #ember960

```

As it is overriding the background color to be `#f4f4f4`, which is white-washing it

Also, you should not use any `#ember...` ids in your CSS rules, as those IDs are not guaranteed. Thus why it only happens when directly visiting the page versus navigating to it.

---

_[View the full topic](https://meta.discourse.org/t/targeting-ember-css-ids-results-in-weird-behavior/60628)._
