Guppy: if not, a simple.

Ellias: And the colors are always red and blue ?

Virts: No, those are just examples.

Bortner: I mean, just 2 colors ?

Lowthert: Just two conflicting style effects for .foo and .bar.

Ouimet: Each one being constant.

Fenton: Redlizard: ?

Levy: Redlizard: like this?

Marzili: Fenton: Interesting. but I don’t *think* I can get away with relying on . Let me think about this.

Schilsky: Meese: Not really. The key ingredients are 1 links that are descendents not necessarily direct children of .foo and .bar, and 2 arbitrary nesting.

Splawn: Fenton: On second thought, I definitely can’t. It should work for arbitrary “a” descendents, not just direct children.

Fenton: Is this a thought exercise, or is there a real-world purpose to this?

Leaton: It’s a real-world practical problem.

Woolhiser: I’ll spare you the details, but I’m pretty sure the rarified example I posted here adds generality or complications I don’t need.

Fenton: Then you’re stuck with cascading styles. Best approach is to give a cl*** to the links

Ingwell: Create I’m-somewhere-inside-foo and I’m-somewhere-inside-bar cl***es?

Krings: Well, one of the two should do, I think.

Fenton: No, just red and blue would suffice

Gosha: That’s a semantical difference once.

Cobble: Fenton: So, I take it there’s no clean way to do this?

Fenton: I’m sure you’ve seen the effect of conflicting selectors, which is why you’re here. Adding cl***es to the things that you want styled will keep it sane

Fenton: Using would give you a nice clean solution to that, but you’ve said that it would not apply to the real-world case

Barr: Semantically, what I’m trying to write is .foo { a { color: red; } } .bar { a { color: blue; } } . It sounds hard to imagine that css cannot express this, as this sort of structure is the whole point of css.

Fenton: You can express it, but you get in the situation where equally-weighted selectors are both applied, and the one declared last “wins”

Bowmer: Which means I’m not expressing the semantics I’m after.

Cusanelli: I’m expressing something subtly different.

Fenton: CSS does not express any semantics

Fenton: And adding cl***es is not going to affect that

Tofte: Not really what I meant.

Leinweber: Seinnd_: very nice idea, thanks

Leinweber: I will try to do the workaround with background-attachment: fixed;

Justinger: Leinweber:

Heusley: Is it possible to make iframe content responsive with css only? height-wise

Trest: I google but only find solutions for embedding the iframe but not about the content itself

Senko: Is it possible to use id and css together ?

Leinweber: If I do background-size: 100%; is it 100% of the element or 100% of window?

Ernst: Can I use DIV cl*** and ID together in CSS?

Stodomingo: Mosaq21_: sure you can

Rakyta: Stodomingo: how can I do that.

Stodomingo: Have you tried something that didn’t work?

Hunnicut: Background-color: black;

Seltzen: Stodomingo, Preferred live pastebins:

Prvitt: Stodomingo, Cascade is the C in CSS • Spec:

Leinweber: Https:// I think I made it with little bit of JS

Guppy: How do I make the first div take up the entire space up to the second div?

Justinger: Guppy: can you change the order of the HTML elements?

Justinger: Guppy: if not, a simple method is If you can, you can just put the world div first, then remove the float for the hello div and replace it with ‘overflow: hidden’