Cannot change styles anymore

12 views
Skip to first unread message

Michael Heuberger

unread,
Nov 6, 2013, 6:55:03 PM11/6/13
to chromedev...@googlegroups.com
Hi guys

Weird, in Chrome 30.0.1599.114 under Ubuntu 13.10 I cannot edit the styles of HTML elements anymore (in tab Elements).

When I attempt to disable a style, nothing happens. No UI update. When I add a new CSS property, nothing happens.

Hmmm, unable to work. Will have to switch to Firefox temporarily.

Hope anyone can help me or confirm, it's a bug?

Cheers
Michael

Alexander Pavlov

unread,
Nov 7, 2013, 2:01:43 AM11/7/13
to chromedev...@googlegroups.com
Hey Michael,

Is CSS editing broken for you on all pages? If you recently updated your Chrome, have you restarted it? Can you try coming up with a publicly shareable case where this issue is reproduced and share it with us (or with me only, if the code is more or less proprietary)?


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



--
-alexander

Michael Heuberger

unread,
Nov 7, 2013, 6:40:37 PM11/7/13
to chromedev...@googlegroups.com
No, CSS editing works on all other pages. Just not on localhost for the site I am currently working on.

Ofc I have restarted Chrome, still no success. Unable to edit CSS at all. It is the latest Chrome version.

Does this have something to do with the fact that I am working on localhost and that the site is in HTTPS?

Can I somehow look into Chrome's internal log files?
You received this message because you are subscribed to a topic in the Google Groups "chromedevtools-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/chromedevtools-dev/k-llZZAS_b8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chromedevtools-...@googlegroups.com.

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

-- 

Binary Kitchen
Michael Heuberger
4c Dunbar Road
Mt Eden
Auckland 1024
(New Zealand)

Mobile (text only) ...  +64 21 261 89 81
Email ................  mic...@binarykitchen.com
Website ..............  http://www.binarykitchen.com

Alexander Pavlov

unread,
Nov 8, 2013, 3:47:55 AM11/8/13
to chromedev...@googlegroups.com
Michael,

The page scheme should not affect your ability to edit CSS. It's most probably some specifics of your CSS code are in the game. Your best bet now is extracting a minimal case from your HTML+CSS, where the editing would still fail.

In order to see if there are any errors in the DevTools JS code, you can inspect the DevTools window: undock it and hit Ctrl+Shift+I with the DevTools window focused. A new DevTools window will pop up. Check its console for error messages and send them my way, should there be any.

Michael Heuberger

unread,
Nov 10, 2013, 9:50:44 PM11/10/13
to chromedev...@googlegroups.com
Here you go Alexander. In that test.html you see tons on Inline CSS. Ignore the missing background images.

Just open this file in Google Chrome and navigate to the first <form> element with the class "accountDetails". Try to edit its CSS, for example add a 'float: right' ... you see, nothing happens.

But if I edit the styles for the <form> itself, it works. But not not form.accountDetails ... weird.

I hope you can reproduce this on your local machine too?


On Friday, 8 November 2013 21:47:55 UTC+13, Alexander Pavlov wrote:
Michael,

The page scheme should not affect your ability to edit CSS. It's most probably some specifics of your CSS code are in the game. Your best bet now is extracting a minimal case from your HTML+CSS, where the editing would still fail.

In order to see if there are any errors in the DevTools JS code, you can inspect the DevTools window: undock it and hit Ctrl+Shift+I with the DevTools window focused. A new DevTools window will pop up. Check its console for error messages and send them my way, should there be any.
On Fri, Nov 8, 2013 at 3:40 AM, Michael Heuberger <michael....@binarykitchen.com> wrote:
No, CSS editing works on all other pages. Just not on localhost for the site I am currently working on.

Ofc I have restarted Chrome, still no success. Unable to edit CSS at all. It is the latest Chrome version.

Does this have something to do with the fact that I am working on localhost and that the site is in HTTPS?

Can I somehow look into Chrome's internal log files?


On 07/11/13 20:01, Alexander Pavlov wrote:
Hey Michael,

Is CSS editing broken for you on all pages? If you recently updated your Chrome, have you restarted it? Can you try coming up with a publicly shareable case where this issue is reproduced and share it with us (or with me only, if the code is more or less proprietary)?
On Thu, Nov 7, 2013 at 3:55 AM, Michael Heuberger <michael.heuberger.binary...@gmail.com> wrote:
Hi guys

Weird, in Chrome 30.0.1599.114 under Ubuntu 13.10 I cannot edit the styles of HTML elements anymore (in tab Elements).

When I attempt to disable a style, nothing happens. No UI update. When I add a new CSS property, nothing happens.

Hmmm, unable to work. Will have to switch to Firefox temporarily.

Hope anyone can help me or confirm, it's a bug?

Cheers
Michael
--
You received this message because you are subscribed to the Google Groups "chromedevtools-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedevtools-dev+unsub...@googlegroups.com.

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



--
-alexander
--
You received this message because you are subscribed to a topic in the Google Groups "chromedevtools-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/chromedevtools-dev/k-llZZAS_b8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chromedevtools-dev+unsub...@googlegroups.com.

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

-- 

Binary Kitchen
Michael Heuberger
4c Dunbar Road
Mt Eden
Auckland 1024
(New Zealand)

Mobile (text only) ...  +64 21 261 89 81
Email ................  mic...@binarykitchen.com
Website ..............  http://www.binarykitchen.com

--
You received this message because you are subscribed to the Google Groups "chromedevtools-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedevtools-dev+unsub...@googlegroups.com.

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



--
-alexander
test.html

Michael Heuberger

unread,
Nov 10, 2013, 9:53:22 PM11/10/13
to chromedev...@googlegroups.com
Just tried that. Undocked the Dev Tools and reloaded the page. No change, no errors.

Alexander Pavlov

unread,
Nov 11, 2013, 3:32:35 AM11/11/13
to chromedev...@googlegroups.com
Thanks for the case, Michael.

We have identified the issue (filed as https://code.google.com/p/chromium/issues/detail?id=317499). Should be fixed shortly.


On Mon, Nov 11, 2013 at 6:53 AM, Michael Heuberger <michael.heuberg...@gmail.com> wrote:
Just tried that. Undocked the Dev Tools and reloaded the page. No change, no errors.

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



--
-alexander

Michael Heuberger

unread,
Nov 11, 2013, 4:19:56 AM11/11/13
to chromedev...@googlegroups.com
Cool. What was the issue? Is Chrome unable to parse '-moz-focus-inner'?

And when is the update planned?
You received this message because you are subscribed to a topic in the Google Groups "chromedevtools-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/chromedevtools-dev/k-llZZAS_b8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chromedevtools-...@googlegroups.com.

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

-- 

Binary Kitchen
Michael Heuberger
4c Dunbar Road
Mt Eden
Auckland 1024
(New Zealand)

Mobile (text only) ...  +64 21 261 89 81
Email ................  mic...@binarykitchen.com
Website ..............  http://www.binarykitchen.com

Alexander Pavlov

unread,
Nov 11, 2013, 8:31:30 AM11/11/13
to chromedev...@googlegroups.com
Chrome is able to correctly ignore this Moz-specific selector, but the devtools-specific part of the source model building code fails to correctly recover from that "bad" rule in this particular case (due to a combination of a few conditions). Should be fixed in the next canary build.

Michael Heuberger

unread,
Nov 11, 2013, 7:10:29 PM11/11/13
to chromedev...@googlegroups.com
I get it. Makes sense.

Thx Alex!

Totty s

unread,
Mar 14, 2014, 1:03:41 PM3/14/14
to chromedev...@googlegroups.com
Hello!

I still have this problem today :/


On Tuesday, November 12, 2013 12:10:29 AM UTC, Michael Heuberger wrote:
I get it. Makes sense.

Thx Alex!

On 12/11/13 02:31, Alexander Pavlov wrote:
Chrome is able to correctly ignore this Moz-specific selector, but the devtools-specific part of the source model building code fails to correctly recover from that "bad" rule in this particular case (due to a combination of a few conditions). Should be fixed in the next canary build.
On Mon, Nov 11, 2013 at 1:19 PM, Michael Heuberger <michael....@binarykitchen.com> wrote:
Cool. What was the issue? Is Chrome unable to parse '-moz-focus-inner'?

And when is the update planned?


On 11/11/13 9:32 pm, Alexander Pavlov wrote:
Thanks for the case, Michael.

We have identified the issue (filed as https://code.google.com/p/chromium/issues/detail?id=317499). Should be fixed shortly.
On Mon, Nov 11, 2013 at 6:53 AM, Michael Heuberger <michael.heuberger.binary...@gmail.com> wrote:
Just tried that. Undocked the Dev Tools and reloaded the page. No change, no errors.
--
You received this message because you are subscribed to the Google Groups "chromedevtools-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedevtools-dev+unsub...@googlegroups.com.

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



--
-alexander
--
You received this message because you are subscribed to a topic in the Google Groups "chromedevtools-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/chromedevtools-dev/k-llZZAS_b8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chromedevtools-dev+unsub...@googlegroups.com.

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

-- 

Binary Kitchen
Michael Heuberger
4c Dunbar Road
Mt Eden
Auckland 1024
(New Zealand)

Mobile (text only) ...  +64 21 261 89 81
Email ................ mic...@binarykitchen.com Website .............. http://www.binarykitchen.com
--
You received this message because you are subscribed to the Google Groups "chromedevtools-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedevtools-dev+unsub...@googlegroups.com.

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



--
-alexander
--
You received this message because you are subscribed to a topic in the Google Groups "chromedevtools-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/chromedevtools-dev/k-llZZAS_b8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chromedevtools-dev+unsub...@googlegroups.com.

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

Totty s

unread,
Mar 14, 2014, 1:34:28 PM3/14/14
to chromedev...@googlegroups.com
The problem was:

@media screen and (min-width: 600px){
    font-size   : 25px;
    margin      : 15px;
}

The font-size was in the @media and not within a selector. Chrome should make some kind of warning about it. 

Thanks
Reply all
Reply to author
Forward
0 new messages