Inspector not making live adjustments

[Puma10]

Hello all and thanks in advance. 

For some reason I can't make the css updates commit to the live browser window.  Example:

Developer tools says the following

.someClass {

padding: 20px

}

I want to update to 40 px.  I  update and hit enter.  After hitting enter the value of 20px is still present.  

See http://www.jpswebsites.com/dev_tsb/ for examples.

Thanks a lot in advance 

[Vsevolod Vlasov]

Thank you for your report, 

Could you please provide your browser version?

--
Thank you,

Vsevolod Vlasov (vse...@google.com)

[jmou...@gmail.com]

This is happening in Version 22.0.1229.79

Also the search bar in the inspector is gone now.  What the heck!  ONE DAY IT'S THERE, ONE DAY IT'S NOT.

MAKES IT VERY DIFFICULT TO DEVELOP USING CHROME!

[Alexander Pavlov]

On Tue, Oct 2, 2012 at 7:23 PM, <jmou...@gmail.com> wrote:

This is happening in Version 22.0.1229.79

Thanks for the heads-up. The issue has been diagnosed (tracked at https://bugs.webkit.org/show_bug.cgi?id=98246) and is pending a fix.

This occurs on broken stylesheets. In particular, for http://www.jpswebsites.com/dev_tsb/ style.css contains the following snippet at line 747:

/*==============================================//

// CONTENT - GENERAL

//==============================================*/

body{

background:

url(images/curtain.png) repeat-x,

url(images/logo_light.png) no-repeat center top,

url(images/retina_wood.png);

}

font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;

padding: 30px 0 60px 0;

width: 100%;

color: #666666;

}

which is clearly broken.

P.S. One-line '//'-style comments are not valid for CSS.

--
-alexander

[Vsevolod Vlasov]

Could you please provide an example URL and scenario?

On Tue, Oct 2, 2012 at 7:23 PM, <jmou...@gmail.com> wrote:

[rossc...@gmail.com]

I am having the same problem, the inspector is not making live updates. My CSS is all valid.

[Vsevolod Vlasov]

Please provide a URL

[jonatha...@gmail.com]

I too am having this issue. I'm sorry but I cannot replicate the source as the site is behind a firewall. Here is my test CSS: 

/* shakeout BC thing */

#shakeout {

background: url('https://gww.gov.bc.ca/sites/default/files/images/shakeout_bg.jpg') repeat #696a6c;

width: 100%;

height: 220px;

display: none;

*overflow:hidden;

*zoom: 1;

}

#shakeoutInner {

background: url('https://gww.gov.bc.ca/sites/default/files/images/shakeout.jpg') no-repeat;

background-position: 0 -3px;

margin: 0 auto;

width: 900px;

height: 220px;

}

#triggerAftershock, #closeShakout {

cursor: pointer;

margin-top: 151px;

margin-left: 99px;

}

#closeShakout {

float: right;

margin-top: 5px;

margin-right: 5px;

}

#shakeoutInner .shakeoutCopy {

color: white;

float: right;

font-size: 33px;

font-weight: bold;

padding-top: 4px;

position: relative;

  right: -17px;

margin-top: 11px;

/* zoom: 1;

font-style: italic; */

}

#shakeoutInner .shakeoutCopy a {

color: white;

text-decoration: underline;

}

#shakeoutInner .shakeoutCopy a:hover {

color: #df4426;

}

.shakeoutCopy .shakeoutDate {

font-size: 23px;

line-height: 47px;

padding-left: 102px;

}

On Monday, October 1, 2012 4:56:56 PM UTC-7, Puma10 wrote:

[jonatha...@gmail.com]

Sorry Chrome version = 22.0.1229.94 m

[Alexander Pavlov]

Jonathan,

Editing this stylesheet through the CSSOM (Styles sidebar) works for me on Chrome 23.0.1271.26 and should get fixed in your stable Chrome with the next update. Please see http://code.google.com/p/chromium/issues/detail?id=152636 for the reference. Should it still fail in your case after the update, please file a new bug at http://new.crbug.com and specify "DevTools: " at the start of the summary.

--
-alexander

[esteva...@gmail.com]

I'm going to go ahead and chime in as well.  Chrome's inspector has not been working for me for several weeks.

I'm using v. 22.0.1229.94

Live updates within the inspector regarding HTML or styles have not worked at all.

On Monday, October 1, 2012 4:56:56 PM UTC-7, Puma10 wrote:

[joelk...@gmail.com]

I'm also having this issue. Looked at my style sheets until my eyes were bleeding. Ran them through W3C, only got IE filter errors back (to be expected). I can't edit styles, and the only thing that I can do is add inline styles, which is annoying when trying to toggle a specific style. 

Windows 8

Version 22.0.1229.94 m

[Vsevolod Vlasov]

Could you please provide some details like url or code sample?

Please tell us what exactly you are doing, otherwise it's hard to help you.

[Vsevolod Vlasov]

Could you please provide some details like url or code sample?

Please tell us what exactly you are doing, otherwise it's hard to help you.

[John J Barton]

I encountered one cause for this behavior: two CSS rules with the same selector.  Devtools edits the first; chrome applies the second.

jjb

On Dec 17, 2012 9:19 PM, <emac...@tapiture.com> wrote:

I have been having this issue for the past few months. It happens on about 50% of the sites I visit.

Is this caused by invalid CSS? If so, what in particular causes it? I have validated my CSS and aren't finding any errors or flags.

On Monday, October 1, 2012 4:56:56 PM UTC-7, Puma10 wrote:

[mhen...@gmail.com]

Same issue here, Version 24.0.1312.52 m, Windows 8

[mhen...@gmail.com]

Updated to Version 24.0.1312.56 m, same issue on all websites

[Vsevolod Vlasov]

Could you please provide a specific url and reproduction scenario for this issue? Otherwise it is hard to reproduce it and identify the problem.

On Tue, Dec 18, 2012 at 7:32 AM, <emac...@tapiture.com> wrote:

I have been having this issue for the past few months. It happens on about 50% of the sites I visit.

Is this caused by invalid CSS? If so, what in particular causes it? I have validated my CSS and aren't finding any errors or flags.

On Monday, October 1, 2012 4:56:56 PM UTC-7, Puma10 wrote:

[Vsevolod Vlasov]

Could you please provide a specific url and reproduction scenario for this issue? Otherwise it is hard to reproduce it and identify the problem.

[kuub...@gmail.com]

On this page (https://groups.google.com/forum/#!topic/google-chrome-developer-tools/f_my2L9ktu8) I open Developer Tools > I select a div or p on the page and in the Inspector, in element.style {, I type "font-size:50px;" without the "" of course.

It lets me type but as soon as I click next to the line it's gone.

I have switched between Chrome versions, re-installed etc. Nothing works.

[PhistucK]

Works for me. I tried to set the mentioned style for the title of one of the posts.

Chrome 24 on Windows XP.

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[kuub...@gmail.com]

It's supposed to work, that's why I posted the problem here, because for me it doesn't work, nor does it work on any other website : )

[kuub...@gmail.com]

attached are two screens... in the Inspector CSS stzle sheet I can change the bg color to red, but not in the Inspector itself.

[PhistucK]

You never mentioned your Chrome/Chromium version and platform, which might be helpful.

☆PhistucK

On Tue, Jan 29, 2013 at 5:06 PM, <kuub...@gmail.com> wrote:

attached are two screens... in the Inspector CSS stzle sheet I can change the bg color to red, but not in the Inspector itself.

--

[kuub...@gmail.com]

Version 24.0.1312.56 m, Windows 8. I don't have the problem on my Windows 8 laptop though, same Chrome version.

[nift...@gmail.com]

Potential fix If you have validated your CSS:  

I had the same problem.  I also noticed in the console an error message regarding my style sheet (on some page loads): "Resource interpreted as Image but transferred with MIME type text/css"

It appears to be a slight file corruption.

I use notepad++ but I have not tracked it down definitely as the source of this problem (and other quirky issues with files I frequently edit and upload).  In any case, notepad++ does not seem to handle this 'slight corruption' as I'm calling it.

ACTION: In all cases, I have been able to create a NEW file (Save-As does NOT work), copy and paste the contents, then delete the oldfile.  I rename the new file to the old and FTP to the same location.

Voila.  Stuff starts working again.  It's saved by butt more than twice.  Good luck.

[Vsevolod Vlasov]

Could you please try opening inspector on inspector (by pressing ctrl+shift+i in inspector in undocked mode) and see if there are any errors in console when you try to play with your CSS styles?

--

[bruno...@ijunior.com.br]

I am having the same issue

Chrome 22.0.1229.79 - Ubuntu 12.10

[O_Vigilante]

Hello,

I had the same problem one day to the other and now I found what the problem was.

Like apa...@chromium.org says it "occurs on broken stylesheets."

My problem was that I wrote "background:url() no-repeat center top" but I don't wrote the path or name of an image, causing this issue.

Problem solved for me.

Thanks,

[mhen...@gmail.com]

I have the same issue since a while, updating Chrome does not solve the problem. At my home pc all works fine, on office pc is won't work.

Both have Windows 8, Chrome Version 26.0.1410.64 m.

Problem occurs on all websites, broken style sheets are not the issue.

Mike

[ieud...@gmail.com]

Thanks! That's what I did too. I put url() as a placeholder, since I hadn't created the background image yet.

Didn't know chrome's inspector would be like, "Nope. I won't work unless you put something in there. hhmmph."

I just put "asgsdg" and it worked again.

[sina.k...@gmail.com]

Just adding a note here, I was having the same problem and the issue was that I had url() somewhere in my CSS. Removed it and now everything's fixed.

[ericne...@gmail.com]

I'm experiencing the same issue.

Version 28.0.1500.72 m

I'm not able to modify styles to get them right.

Same at home computer (and same Chrome version)

[ericne...@gmail.com]

But on that http://www.jpswebsites.com/dev_tsb/, I was able to modify the styles in the inspector... weird.

[PhistucK]

Do you have an empty URL function (url()) within your CSS by any chance? if so, it may cause such issues (and it is redundant anyway), so you better remove it.

☆PhistucK

--

[arafat...@yahoo.com]

My vr is Version 29.0.1547.66 m

Ok like others i cannot also edit live CSS.

The fact is Chrome make 100% valid and URL() free css Live Editable that you can only edit site like facebook, google, lol... do you think everyone develop only that site???

The fact is developer need this tools for the non-valid and bad CSS, this is not a tools for developing CSS, we use this tools to check CSS temporary.

And i believe this is the big issue why max developer choose Chrome, But if Chrome do not fix this bloody function ASAP then i can assure that 50% developer will bound to leave Chrome.

As this looks like funny but this is true that 90% developer use chrome mainly for this CSS flexibility, And once you cut this means you cut your own finger!!!

Shame on you Chrome!!!

On Tuesday, October 2, 2012 2:37:00 PM UTC+6, Vsevolod Vlasov wrote:

Thank you for your report, 

Could you please provide your browser version?

On Tue, Oct 2, 2012 at 3:56 AM, Puma10 <joshw...@gmail.com> wrote:

Hello all and thanks in advance. 

For some reason I can't make the css updates commit to the live browser window.  Example:

Developer tools says the following

.someClass {

padding: 20px

}

I want to update to 40 px.  I  update and hit enter.  After hitting enter the value of 20px is still present.  

See http://www.jpswebsites.com/dev_tsb/  for examples.

Thanks a lot in advance 

[mfrob...@tampabay.com]

At least in my case, this line

@viewport { width: device-width; }

was breaking Chrome inspector. 

Since we're using meta viewport tags anyway, I commented it out. I have a separate line for IE10, 

@-ms-viewport { width: device-width; }

which doesn't affect Chrome.

Mac, Version 29.0.1547.65 but this has been going on for a few versions/weeks (the @viewport tag has been in our CSS much longer than that.)

Chrome Inspector is much faster than Firebug and I missed it. Nice to have it working on tampabay.com again. Or it will be, as soon as I deploy this fix...

[Vsevolod Vlasov]

This was fixed a few days ago: https://code.google.com/p/chromium/issues/detail?id=278289 . It should reach canary channel within a couple of days (if not yet)

--

[Vsevolod Vlasov]

Could you please check if you have @viewport rules in your CSS?

Could you give us some more details?

If you could provide a particular URL where this happens for you (or the stylesheet contents) we could investigate further.

[babb...@googlemail.com]

I've been having the same problems with Chrome for the last few versions. I've just updated to 29.0.1547.76 m and it's still broken.

I use the 320andup mobile framework and there are several CSS values that seem to now choke Chrome. If I comment these out, I can edit values again. I always thought that CSS was ignored if not understood but it seems not. The problematic values include:

input::-moz-placeholder { 

.font-size(14); }

-webkit-overflow-scrolling : touch; 

@-moz-viewport { 

width : device-width; }

@-ms-viewport { 

width : device-width; }

@-o-viewport { 

width : device-width; }

@viewport { 

width : device-width; }

[babb...@googlemail.com]

Further to my post above here is a sample URL where this doesn't work - http://www.scienceboffins.co.uk/

[zerodeg...@gmail.com]

I have the same issue, latest version of Chrome on Windows 7. Getting pretty frustrated now!

[Pavel Feldman]

Please update Chrome to latest stable (version 30), things should work fine there.

Regards

Pavel

--

You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/41d1fa2b-b130-4018-a9bc-92280493b0f3%40googlegroups.com.

[babb...@googlemail.com]

Hi Pavel,

I've just updated to 30.0.1599.66 m and this appears to have fixed it. Nice one!

Pete

On Wednesday, 2 October 2013 15:55:35 UTC+1, pfeldman wrote:

Please update Chrome to latest stable (version 30), things should work fine there.

Regards

Pavel

On Wed, Oct 2, 2013 at 10:58 AM, <zerodeg...@gmail.com> wrote:

I have the same issue, latest version of Chrome on Windows 7. Getting pretty frustrated now!

On Wednesday, September 25, 2013 11:05:44 AM UTC+2, babb...@googlemail.com wrote:

Further to my post above here is a sample URL where this doesn't work - http://www.scienceboffins.co.uk/

On Wednesday, 25 September 2013 10:03:22 UTC+1, babb...@googlemail.com wrote:

I've been having the same problems with Chrome for the last few versions. I've just updated to 29.0.1547.76 m and it's still broken.

I use the 320andup mobile framework and there are several CSS values that seem to now choke Chrome. If I comment these out, I can edit values again. I always thought that CSS was ignored if not understood but it seems not. The problematic values include:

input::-moz-placeholder { 

.font-size(14); }

-webkit-overflow-scrolling : touch; 

@-moz-viewport { 

width : device-width; }

@-ms-viewport { 

width : device-width; }

@-o-viewport { 

width : device-width; }

@viewport { 

width : device-width; }

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.

[rhrac...@gmail.com]

Hello:

I'm on Chrome on a Mac (Version 30.0.1599.66) and I no longer seem to be able to make live edits on the CSS. Is this a bug?

Cheers, Russell

[Vsevolod Vlasov]

Could you please provide more details?

--

You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/05e1868f-9762-49ce-b119-c4e79a858e7e%40googlegroups.com.

[eba...@gmail.com]

Not only can I not make live edits - the Inspect tool has stopped showing me a great deal of code needed to make edits. Simple things like entry-header background color. What's up with this?

[Alexander Pavlov]

Hello there!

On Sat, Oct 12, 2013 at 8:45 AM, <eba...@gmail.com> wrote:

Not only can I not make live edits - the Inspect tool has stopped showing me a great deal of code needed to make edits. Simple things like entry-header background color. What's up with this?

It is plain impossible for us to answer this question, unless you can provide extended info about your setup and a sample of your code where DevTools are failing. Feel free to mail me in private in case the affected code is non-public.

 

On Monday, October 1, 2012 7:56:56 PM UTC-4, Puma10 wrote:

Hello all and thanks in advance. 

For some reason I can't make the css updates commit to the live browser window.  Example:

Developer tools says the following

.someClass {

padding: 20px

}

I want to update to 40 px.  I  update and hit enter.  After hitting enter the value of 20px is still present.  

See http://www.jpswebsites.com/dev_tsb/ for examples.

When loading, this page gives quite a few errors (GET http://www.jpswebsites.com/dev_tsb/flexslider.css 404 (Not Found), GET http://www.jpswebsites.com/dev_tsb/jquery.flexslider.js 404 (Not Found), Uncaught SyntaxError: Unexpected token < for http://www.theteeshirtbakery.com/wp-content/plugins/royalslider/js/jquery.royal-slider.min.js?ver=1.0) and a few similar ones. The page is not styled for me at all (since flexslider.css is 404).

 

Thanks a lot in advance 

--

You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/14dbd49e-8b5d-48ee-b8f3-d858e319dbf3%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
-alexander

[andrew....@gmail.com]

Hi,

I was having these same issues - live css updates had stopped working. However, this was not just in Chrome but also in Firefox with Firebug.

It occurred to me that I had changed my workflow from using BBEdit as my main text editor to using Sublime Text 2 together with CodeKit (as I was editing .less files and compiling them with CodeKIt).

I believe this setup was 'stealing' the live update facility from the browsers as the live updating was happening once changes to the .less file and hence the corresponding .css files had completed.

Hence, I reverted back to my original workflow (not ideal because I like the code highlighting im Sublime Text)

and live css updates within Firefox and Chrome started to work again!

[uxha...@gmail.com]

I'm having the same issue... No issue in Firefox or in Chrome Canary though. Very weird!

Den måndagen den 14:e oktober 2013 kl. 11:36:01 UTC+2 skrev apa...@chromium.org:

Hello there!

On Sat, Oct 12, 2013 at 8:45 AM, <eba...@gmail.com> wrote:

Not only can I not make live edits - the Inspect tool has stopped showing me a great deal of code needed to make edits. Simple things like entry-header background color. What's up with this?

It is plain impossible for us to answer this question, unless you can provide extended info about your setup and a sample of your code where DevTools are failing. Feel free to mail me in private in case the affected code is non-public.

 

On Monday, October 1, 2012 7:56:56 PM UTC-4, Puma10 wrote:

Hello all and thanks in advance. 

For some reason I can't make the css updates commit to the live browser window.  Example:

Developer tools says the following

.someClass {

padding: 20px

}

I want to update to 40 px.  I  update and hit enter.  After hitting enter the value of 20px is still present.  

See http://www.jpswebsites.com/dev_tsb/ for examples.

When loading, this page gives quite a few errors (GET http://www.jpswebsites.com/dev_tsb/flexslider.css 404 (Not Found), GET http://www.jpswebsites.com/dev_tsb/jquery.flexslider.js 404 (Not Found), Uncaught SyntaxError: Unexpected token < for http://www.theteeshirtbakery.com/wp-content/plugins/royalslider/js/jquery.royal-slider.min.js?ver=1.0) and a few similar ones. The page is not styled for me at all (since flexslider.css is 404).

 

Thanks a lot in advance 

--

You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/14dbd49e-8b5d-48ee-b8f3-d858e319dbf3%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
-alexander

[hannes.j...@gmail.com]

I still have this problem on:

* Windows 8, Chrome  Version 31.0.1650.63 m 

* OSX Mavericks, Chrome Version 31.0.1650.63

I don't have the problem on on:

* Windows 8 Chrome Version 34.0.1781.0 canary

 

I've tried the following with no luck:

* CSS now validates with W3C validator (I removed any calc attributes, ::selection selectors etc).

* Disabled javascript (to check that there's no wonky css inserted through js).

* Copied CSSand pasted into fresh .css file saved with notepad (to avoid encoding errors).

Is the issue still being worked on? Is there anything I can do to help? I can't post the page I'm working on in public but I can do it privately.

Sincerily,

Hannes

On Friday, November 2, 2012 1:25:39 PM UTC+1, Vsevolod Vlasov wrote:

Could you please provide some details like url or code sample?

Please tell us what exactly you are doing, otherwise it's hard to help you.

On Wed, Oct 31, 2012 at 9:45 AM, <esteva...@gmail.com> wrote:

I'm going to go ahead and chime in as well.  Chrome's inspector has not been working for me for several weeks.

I'm using v. 22.0.1229.94

Live updates within the inspector regarding HTML or styles have not worked at all.

On Monday, October 1, 2012 4:56:56 PM UTC-7, Puma10 wrote:

Hello all and thanks in advance. 

For some reason I can't make the css updates commit to the live browser window.  Example:

Developer tools says the following

.someClass {

padding: 20px

}

I want to update to 40 px.  I  update and hit enter.  After hitting enter the value of 20px is still present.  

See http://www.jpswebsites.com/dev_tsb/ for examples.

Thanks a lot in advance 

--

[PhistucK]

The validator accepts empty URL functions -

background-image: url();

Make sure you do not have any of "url()", 'url("")' or "url('')", because they may screw up the Developer Tools.

(I am not sure this issue still exists?)

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/02ce8d78-98f4-4d49-8b09-a220ceaaa191%40googlegroups.com.

[ga...@webstuff.ie]

I'm having the same issue, In chrome V 32.0.1700.77 I was able to test a few versions of chrome and the its introduced since V28. Using OSX and whilst the stylesheet contains a lot of warnings there are no parse errors detected. 

[PhistucK]

Can you try isolating the erroneous rule? remove CSS until live adjustment is working again and post the smallest test case to crbug.com?

☆PhistucK

--

You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/d972a884-091d-4159-86da-9f21d3bf051c%40googlegroups.com.

[Milo]

I've also run into this bug with the latest version of chrome. Removing all references to *zoom: 1; from my CSS file fixed the issue. I will try and have a look into putting together a test case later today.

On Monday, 27 January 2014 18:37:15 UTC, PhistucK wrote:

Can you try isolating the erroneous rule? remove CSS until live adjustment is working again and post the smallest test case to crbug.com?

☆PhistucK

On Mon, Jan 27, 2014 at 7:43 PM, <ga...@webstuff.ie> wrote:

I'm having the same issue, In chrome V 32.0.1700.77 I was able to test a few versions of chrome and the its introduced since V28. Using OSX and whilst the stylesheet contains a lot of warnings there are no parse errors detected. 

On Tuesday, October 2, 2012 12:56:56 AM UTC+1, Puma10 wrote:

Hello all and thanks in advance. 

For some reason I can't make the css updates commit to the live browser window.  Example:

Developer tools says the following

.someClass {

padding: 20px

}

I want to update to 40 px.  I  update and hit enter.  After hitting enter the value of 20px is still present.  

See http://www.jpswebsites.com/dev_tsb/ for examples.

Thanks a lot in advance 

--

You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.

[Vsevolod Vlasov]

I can not reproduce it with *zoom:1, could you please provide a test case?

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/90ec40ec-9ce7-4010-9a4b-d17c79327a97%40googlegroups.com.

[justm...@gmail.com]

Thanks for the fix!  I had a placeholder for a background: url(); and all I needed to do was comment it out.

On Wednesday, April 10, 2013 7:54:47 AM UTC-4, O_Vigilante wrote:

Hello,

I had the same problem one day to the other and now I found what the problem was.

Like apa...@chromium.org says it "occurs on broken stylesheets."

My problem was that I wrote "background:url() no-repeat center top" but I don't wrote the path or name of an image, causing this issue.

Problem solved for me.

Thanks,

[fskh...@gmail.com]

Here's a new one:

I get this issue when placing non-webkit prefixed 'input-placeholder' pseudo-selectors inside of a media query.

For example: 

This works -

@media only screen and (max-width: 40em) {

input::-webkit-input-placeholder { -webkit-transition: opacity 0.2s ease-in-out; transition: opacity 0.2s ease-in-out; }

/* input:-moz-placeholder { transition: opacity 0.2s ease-in-out; }

input::-moz-placeholder { transition: opacity 0.2s ease-in-out; }

input:-ms-input-placeholder { transition: opacity 0.2s ease-in-out; }*/

input:focus::-webkit-input-placeholder { opacity: 0; }

/* input:focus:-moz-placeholder { opacity: 0; }

input:focus::-moz-placeholder { opacity: 0; }

input:focus:-ms-input-placeholder { opacity: 0; }*/

}

But this breaks it - 

@media only screen and (max-width: 40em) {

input::-webkit-input-placeholder { -webkit-transition: opacity 0.2s ease-in-out; transition: opacity 0.2s ease-in-out; }

input:-moz-placeholder { transition: opacity 0.2s ease-in-out; }

input::-moz-placeholder { transition: opacity 0.2s ease-in-out; }

input:-ms-input-placeholder { transition: opacity 0.2s ease-in-out; }

input:focus::-webkit-input-placeholder { opacity: 0; }

input:focus:-moz-placeholder { opacity: 0; }

input:focus::-moz-placeholder { opacity: 0; }

input:focus:-ms-input-placeholder { opacity: 0; }

}

Comment out those non -webkit vendor prefixed selectors and it works again. Move them Outside of the media query, and it works again...

Not sure if this is a bug, but I don't see any other issues with my CSS that I'm aware of.

Anyone else have this problem?

[fskh...@gmail.com]

Also, another interesting symptom of this, along with the live editing breaking:

Colors that are defined in your stylesheet as hex colors are displayed as rgb in the inspector window. Nice quick way to check while you're commenting out styles looking for the offending one...

[PhistucK]

If this causes live adjustments to fail, this is definitely a bug.

Can you file a new issue at crbug.com and add this example to it?

Thank you!

☆PhistucK

--

You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/8449b174-aaf6-41f2-947b-e989269758a1%40googlegroups.com.

[fskh...@gmail.com]

Done!

Thanks

☆PhistucK

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.