Quote:
Originally Posted by kovidgoyal
You already know where it is overriden, just look for the same property somewhere where it is not struck out. And FYI, overriden indication is already implemented.
|
Wow! that was a fast ToDo>Done transition...
Nevertheless, what I wanted is somehow merging the info given by Inspector, where you can know every single step in the overriding process (because that's how styles are sorted), and your Live CSS features. I mean knowing in each overridden step/style, which is the setting that actually kills it, despite if that killer setting is itself dead because any other one with higher priority.
With this feature, while looking at nested tags you could also detect CSS style conflicts or troubles in the parent tags or classes. In my own experience it's not so uncommon being looking for style troubles in a deep <span> tag and then noticing that, related or unrelated with them, there are some troubles in the <div> vs <body> relation, at least two steps up.
But I don't know the coding effort involved...
Quote:
Originally Posted by BetterRed
@arspr - Strikeout can be done via the strike BBcode tag
BR
|
Thanks, how did you know? I mean, there's NO button in the interface to do it (I had pressed them all). Is there a wiki page or something like that?