Ta-Da!:
http://jsfiddle.net/VNh3u/178/

I had never heard of this but apparently the problem isn't the vendor 
prefix but the lack of a psuedo-class (I had problems with this when 
developing my site as well and it took me a while to figure out).

Tip of the hat to Chris Coyier: 
http://css-tricks.com/snippets/css/link-pseudo-classes-in-order/  
I definitely have a LoVe HAte relationship with psuedo-classes :)

On Wednesday, February 13, 2013 11:40:52 AM UTC-5, Davis Ford wrote:
>
> I'm building an app for an embedded webkit browser.  It includes the 
> qt-webkit-4.6.2-user-agent.css stylesheet by default, and I don't appear to 
> have any control over that.
>
> I added the latest bootstrap to this app, and I've noticed some quirks, 
> for example <a> links are in browser default blue and contain underlines.
>
> Inspecting the css in Chrome, I can see the bootstrap rules for a have 
> been overridden by the system rules.  It appears that browser prefix pseudo 
> selectors take precedence over other styles regardless of the order they 
> are defined in.
>
> Here's a simple jsfiddle that illustrates said problem:
>
> http://jsfiddle.net/zenocon/VNh3u/177/
>
> The link is blue with an underline despite my rule that says otherwise -- 
> simply by having the pseudoselector a:-webkit-any-link rule in place.
>
> This is my conundrum.  I don't think I have the ability to not include the 
> user-agent stylesheet.  I *can* override this by adding my own rule, e.g.
>
> a:-webkit-any-link {
>   color: #08c;
>   text-decoration: none;
> }
>
> ...but I fear this is one of many such rules, and I'll end up having to 
> repeat a major chunk of the bootstrap css with these browser extension 
> selectors in order to get back to a basic reset that shows bootstrap in its 
> intended state.
>
> Is there any other (smarter) workaround for this?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"twitter-bootstrap" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to