Hello, I've been using the developer tools and getting good use from them. Today for some reason when I make the changes to the CSS of my website in the right panel (Matched CSS Rules) the changes are not processed to the website. They do change, however, when I open the full stylesheet on the left of the page and change in the stylesheet. Only seems to be a problem in the right panel. It does work with other websites, just not mine. Cannot figure out WTF is going on.. perhaps a JS file is bugging it up..??? Any help will be much appreciated.. cheers Andy
Could you please provide an URL of your site and describe which style does
not change?
Could you please provide your browser version also?
Thank you
On Tue, Oct 2, 2012 at 3:23 AM, Andy Findlay <tch...@gmail.com> wrote:
> Hello,
> I've been using the developer tools and getting good use from them.
> Today for some reason when I make the changes to the CSS of my website in
> the right panel (Matched CSS Rules) the changes are not processed to the
> website.
> They do change, however, when I open the full stylesheet on the left of
> the page and change in the stylesheet. Only seems to be a problem in the
> right panel. It does work with other websites, just not mine.
> Cannot figure out WTF is going on.. perhaps a JS file is bugging it up..???
> Any help will be much appreciated..
> cheers
> Andy
I have the exactly same problem and any changes to CSS only take effect when I apply the changes to the full stylesheet. Will find out version number later. (It only happens to one of my two laptops. The other one is working fine... )
On Tuesday, 2 October 2012 09:36:15 UTC+1, Vsevolod Vlasov wrote:
> Could you please provide an URL of your site and describe which style does > not change? > Could you please provide your browser version also?
> Thank you
> On Tue, Oct 2, 2012 at 3:23 AM, Andy Findlay <tch...@gmail.com<javascript:> > > wrote:
>> Hello, >> I've been using the developer tools and getting good use from them. >> Today for some reason when I make the changes to the CSS of my website in >> the right panel (Matched CSS Rules) the changes are not processed to the >> website. >> They do change, however, when I open the full stylesheet on the left of >> the page and change in the stylesheet. Only seems to be a problem in the >> right panel. It does work with other websites, just not mine. >> Cannot figure out WTF is going on.. perhaps a JS file is bugging it >> up..??? >> Any help will be much appreciated.. >> cheers >> Andy
Hello,
I'm using google fonts and my letter-spacing: -0.8px (which works in all other browsers) doesnt work in Chrome, unless I change it to -1px in which case the letter spacing is too close.
Is there a way to have these fonts display in increments of less than 1px?
thanks..!
On Tuesday, October 2, 2012 1:36:15 AM UTC-7, Vsevolod Vlasov wrote:
> Could you please provide an URL of your site and describe which style does > not change? > Could you please provide your browser version also?
> Thank you
> On Tue, Oct 2, 2012 at 3:23 AM, Andy Findlay <tch...@gmail.com<javascript:> > > wrote:
>> Hello, >> I've been using the developer tools and getting good use from them. >> Today for some reason when I make the changes to the CSS of my website in >> the right panel (Matched CSS Rules) the changes are not processed to the >> website. >> They do change, however, when I open the full stylesheet on the left of >> the page and change in the stylesheet. Only seems to be a problem in the >> right panel. It does work with other websites, just not mine. >> Cannot figure out WTF is going on.. perhaps a JS file is bugging it >> up..??? >> Any help will be much appreciated.. >> cheers >> Andy
> On Tuesday, October 2, 2012 1:36:15 AM UTC-7, Vsevolod Vlasov wrote:
>> Could you please provide an URL of your site and describe which style >> does not change? >> Could you please provide your browser version also?
>> Thank you
>> On Tue, Oct 2, 2012 at 3:23 AM, Andy Findlay <tch...@gmail.com> wrote:
>>> Hello, >>> I've been using the developer tools and getting good use from them. >>> Today for some reason when I make the changes to the CSS of my website >>> in the right panel (Matched CSS Rules) the changes are not processed to >>> the website. >>> They do change, however, when I open the full stylesheet on the left of >>> the page and change in the stylesheet. Only seems to be a problem in the >>> right panel. It does work with other websites, just not mine. >>> Cannot figure out WTF is going on.. perhaps a JS file is bugging it >>> up..??? >>> Any help will be much appreciated.. >>> cheers >>> Andy
A co-worker of mine encountered this. It was definitely caused by invalid CSS. In this case url attributes in background rules caused the issue. CSS was pasted in that had background rules. In the rules, "url()" was used with the intention of putting the paths in later. This seemed to confuse the inspector. Chrome won't report it as an error, and the W3C CSS validator didn't report it as an issue either. In this case, he just removed the "url()" form the rule all together and it began working as expected. Hope this helps someone else.
On Tue, Oct 16, 2012 at 11:10 PM, Adam Plante <apla...@allwebcafe.com>wrote:
> A co-worker of mine encountered this. It was definitely caused by invalid
> CSS. In this case url attributes in background rules caused the issue. CSS
> was pasted in that had background rules. In the rules, "url()" was used
> with the intention of putting the paths in later. This seemed to confuse
> the inspector. Chrome won't report it as an error, and the W3C CSS
> validator didn't report it as an issue either. In this case, he just
> removed the "url()" form the rule all together and it began working as
> expected. Hope this helps someone else.
Thanks Adam. We implemented an empty background url on paragraph and heading tags to fix an issue with width sizing on Android devices. We then could not work out why we could no longer inspect any elements!
On Tuesday, 16 October 2012 20:11:00 UTC+1, Adam Plante wrote:
> A co-worker of mine encountered this. It was definitely caused by invalid > CSS. In this case url attributes in background rules caused the issue. CSS > was pasted in that had background rules. In the rules, "url()" was used > with the intention of putting the paths in later. This seemed to confuse > the inspector. Chrome won't report it as an error, and the W3C CSS > validator didn't report it as an issue either. In this case, he just > removed the "url()" form the rule all together and it began working as > expected. Hope this helps someone else.
On Mon, Nov 19, 2012 at 4:03 PM, <neil.young2...@gmail.com> wrote:
> Thanks Adam. We implemented an empty background url on paragraph and
> heading tags to fix an issue with width sizing on Android devices. We then
> could not work out why we could no longer inspect any elements!
> We are just commenting them out for now!
> On Tuesday, 16 October 2012 20:11:00 UTC+1, Adam Plante wrote:
>> A co-worker of mine encountered this. It was definitely caused by invalid
>> CSS. In this case url attributes in background rules caused the issue. CSS
>> was pasted in that had background rules. In the rules, "url()" was used
>> with the intention of putting the paths in later. This seemed to confuse
>> the inspector. Chrome won't report it as an error, and the W3C CSS
>> validator didn't report it as an issue either. In this case, he just
>> removed the "url()" form the rule all together and it began working as
>> expected. Hope this helps someone else.
> On Tue, Oct 16, 2012 at 11:10 PM, Adam Plante <apl...@allwebcafe.com<javascript:> > > wrote:
>> A co-worker of mine encountered this. It was definitely caused by invalid >> CSS. In this case url attributes in background rules caused the issue. CSS >> was pasted in that had background rules. In the rules, "url()" was used >> with the intention of putting the paths in later. This seemed to confuse >> the inspector. Chrome won't report it as an error, and the W3C CSS >> validator didn't report it as an issue either. In this case, he just >> removed the "url()" form the rule all together and it began working as >> expected. Hope this helps someone else.
