4 ms·

What is the deal with those orange buttons that hover on the right hand side of the code snippets? They look like they should be interacted with, but when I ho

What is the deal with those orange buttons that hover on the right hand side of the code snippets? They look like they should be interacted with, but when I hover my mouse over them they fade away. That's terribly irritating.

dominicrodger 14y ago
I'm pretty sure they're just markers telling you what the code is an example of, so they get out of your way when you hover over the code.
- shay-howe 14y ago
  You're correct, thanks for the answer here. Feedback has been hot and cool on them, still trying to decide if they are worth it or not.
  - codegeek 14y ago
    Btw, Does not fade away in IE8 with hover.
    - mixmastamyk 14y ago
      IE8 can't do anything fancy.
  - cdr 14y ago
    Having them pop out of existence is jarring; maybe have them fade to near-invisible.
  - brightghost 14y ago
    I'm not really seeing why I would want the label of the section in question hidden when I'm dealing with it, and at least for me there's not really a parity between 'dealing with' and 'hovering over with my cursor' anyway, unless I'm copying the text. The bright orange color and the constant flashing on/off just adds visual noise and makes it difficult to really read the labels anyway, imo.
jaredmcateer 14y ago
Yup I definitely tried to click them a couple times... they don't fad away for me in Chrome, they just disappear, left me wondering if I needed to play some sort of game to get to them properly.
- mdarens 14y ago
  They don't fade away in Chrome because he's using a pseudo-element in the form of content: attr(title). Gecko supports transitions on generated content and WebKit does not. Also, looking at the ::selection example, it should mentioned that it's not safe to group vendor prefixes in the selector portion of a declaration block, as, unlike with properties, the whole block will be skipped if an unrecognized selector is encountered by a UA's CSS parser.

dominicrodger 14y ago

I'm pretty sure they're just markers telling you what the code is an example of, so they get out of your way when you hover over the code.

shay-howe 14y ago
You're correct, thanks for the answer here. Feedback has been hot and cool on them, still trying to decide if they are worth it or not.
- codegeek 14y ago
  Btw, Does not fade away in IE8 with hover.
  - mixmastamyk 14y ago
    IE8 can't do anything fancy.
- cdr 14y ago
  Having them pop out of existence is jarring; maybe have them fade to near-invisible.
- brightghost 14y ago
  I'm not really seeing why I would want the label of the section in question hidden when I'm dealing with it, and at least for me there's not really a parity between 'dealing with' and 'hovering over with my cursor' anyway, unless I'm copying the text. The bright orange color and the constant flashing on/off just adds visual noise and makes it difficult to really read the labels anyway, imo.

jaredmcateer 14y ago

Yup I definitely tried to click them a couple times... they don't fad away for me in Chrome, they just disappear, left me wondering if I needed to play some sort of game to get to them properly.

mdarens 14y ago
They don't fade away in Chrome because he's using a pseudo-element in the form of content: attr(title). Gecko supports transitions on generated content and WebKit does not. Also, looking at the ::selection example, it should mentioned that it's not safe to group vendor prefixes in the selector portion of a declaration block, as, unlike with properties, the whole block will be skipped if an unrecognized selector is encountered by a UA's CSS parser.