Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Adding new CSS rules doesn’t work in Chrome 19.0.1077.3 dev and above #40

Closed
NV opened this Issue Mar 24, 2012 · 21 comments

Comments

Projects
None yet
5 participants

lajlev commented Apr 11, 2012

Any idea when it gonna be fixed?

Owner

NV commented Apr 11, 2012

No idea. You should ask them on the bug page.

this is a huge bummer.... at least we were able to avoid the problem before 19 hit the main channel.

have either of you two come up with workarounds for now? or is this feature essentially dead?

Owner

NV commented May 18, 2012

Saving new CSS rules for <link rel=stylesheet> inside <body> still works.

groovy. didnt know that was still a contender.

What a fuck.
Sorry.

Nikita, any news? (I've read that bug's thread, see no reaction, whats next? I was using Autosave for editing JavaScript in Scripts, and CSS in Resources. Now the edit button at least is GONE.)

UPD. Leaved deliberately reeking comment in there. I'm in real anger - instead of working, making my websites, I'm now here, posting useless comments, trying to rollback to 18th. Excuse me.

Guys, have you an idea how/where to grab a latest stable 18th?
I need it as .deb for amd64 arch
I was trying to browse the repo directy but it disallows browsing: http://dl.google.com/linux/chrome/deb/

Owner

NV commented May 23, 2012

It looks like full-time Chrome DevTools developers don’t use my extension hence don’t understand the changes they have made.

I was using Autosave for editing JavaScript in Scripts, and CSS in Resources. Now the edit button at least is GONE.

I believe it’s a separate issue. All editable resources are just editable. They removed the edit button. You can save changes by Ctrl-S (Cmd-S on Mac).

Thank you, for noting this. I think you would also agree that having no way to monitor whether a thing is changed and needs posting or not -- is not what one may call usable editor.
To say truth, Nikit, I consider your Autosave as the best wev development tool I've seen since times when FireBug was out.

Owner

NV commented May 25, 2012

Fixed by 627534b

@NV NV closed this May 25, 2012

agreed with aneganov. this tool has been essential to tweaking / updating / tailoring css properties and transitions. a soon to be released project ive been working on for the past year has you to thank.

Owner

NV commented May 25, 2012

Thanks guys :)

On Chrome 21.0.1152.0 canary I can't even edit existing CSS rules, unless the link to the stylesheet is placed inside the body. Is this related?

Actually is seems to be saving the same version of the stylesheet over and over again. Changes are discarded.

Owner

NV commented May 28, 2012

Drag-and-dropping downloaded extension file (latest.crx) to chrome://extensions page works for all version.

Drag-and-dropping downloaded extension file (latest.crx) to chrome://extensions page works for all version.

You probably mistake in the thread.. but always good to know.
Or did yo misunderstood my comment?
I was talking about using the extension, already after being installed

Owner

NV commented May 28, 2012

You probably mistake in the thread.. but always good to know.

Whoops, it supposed to be in #48.

Actually is seems to be saving the same version of the stylesheet over and over again. Changes are discarded

Looks like #54.

is this closed now with the caveat that we still need to have the css included within the body tag?

Owner

NV commented Jun 26, 2012

No, it does work in Chrome 21+. All new CSS rules add to the last included stylesheet as it was before the bug.

NICE!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment