Posted by Seph on February 2, 2013 at 10:15pm
4 followers
| Project: | Live CSS |
| Version: | 7.x-2.9 |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
When I go to use Live CSS and I select a CSS file to edit, I cannot scroll through the file. Before a scroll tab would appear on the side, now there is nothing.
Comments
#1
Thanks for reporting.
- Have you disabled js and css minification on the site?
- Have you waited until the page is finished loading before opening the tab?
If so, is there an error in the JavaScript console at all?
Would be much appreciated to track this down.
#2
I went through the steps you outlined above. js and css minification were both disabled and I waited until the page finished loading. It still didn't work. Then I decided to try using Chrome instead of Safari and it worked. For some reason it isn't appearing or working correctly in Safari.
#3
Hmm, this is odd as it is working fine for me in safari. Which version of Safari are you using? If you open up the console, can you see any JavaScript errors on the page?
Any info to help reproduce would be great.
#4
I am having the same problem i am afraid i cant scroll down.
#5
Can you confirm which browser you are using?
Also ensure you have css and js minification turned off.
If you check the JavaScript console do you see any errors?
#6
sorry guy i am new to this.
I am using the latest version of safari on my macbook.
I dont know how to turn css and js minification off...
#7
It sounds like this is some sort of Safari issue... strangely I'm not seeing it in my Safari though. Have you tried using Chrome instead?
#8
It doesn't work in Safari but in Firefox. Chrome I don't know.
Attached the errors I get in Safari on a page where noting is going on exept a dropdown menu and an image enabled for colorbox. No errors until I click to open the live css drawer.
also:
(242) 42event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future.
#9
It looks like the issue is in the Ace code editor itself.
An update of the Ace editor may well fix the issue in this case.
Patches welcome.