search

beefeather / chromedevtools

Automatically exported from code.google.com/p/chromedevtools
Other
0 stars 0 forks source link

Black foreground color is hard-coded #11

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Google Chrome version:
SDK + Eclipse Debugger version(s):
OS + version:

What steps will reproduce the problem?
1.
2.
3.

What is the expected result?

What happens instead?

Please provide any additional information below. If possible, attach a
(reduced) test-case.

Original issue reported on code.google.com by vrid...@gmail.com on 21 Nov 2009 at 6:51

GoogleCodeExporter commented 8 years ago 
Sorry, sent it too early

Original comment by vrid...@gmail.com on 21 Nov 2009 at 6:53

GoogleCodeExporter commented 8 years ago 
The problem is: black color is hard-coded for non-syntax-highlihgted elements
It makes painful dark code themes using
It would be great to make this customizable

Original comment by vrid...@gmail.com on 21 Nov 2009 at 6:54

GoogleCodeExporter commented 8 years ago 
Hi vridosh

Could you please provide more details? What elements do you mean? In which 
view/editor?

Thanks,
Peter

Original comment by peter.ry...@gmail.com on 23 Nov 2009 at 8:06

GoogleCodeExporter commented 8 years ago 
Hi Peter

Thank you for your response, and sorry for being unclear.
I tried to use Eclipse debugger for Chrome/V8.
It highlights JS syntax, but I can not customize "main" foreground color (so, 
the 
foreground color for elements, that are not recognized by syntax parser). I 
looked at 
code and found it hard-coded there to be always black. If you need more details 
where 
it hard-coded let me know, I can provide them.

Regards,
Vadim Ridosh

Original comment by vrid...@gmail.com on 24 Nov 2009 at 10:02

GoogleCodeExporter commented 8 years ago

Original comment by peter.ry...@gmail.com on 11 Dec 2009 at 12:39

GoogleCodeExporter commented 8 years ago 
Hi Vadim

I'm sorry for slow progress with your issue. Unfortunately, we do not have 
enough 
resources for usability-related stuff. Hopefully, this will be resolved soon.
However, we welcome patches, so if you feel yourself confident in the area, you 
are 
welcome to send us your fix.

Peter

Original comment by peter.ry...@gmail.com on 11 Dec 2009 at 12:43