0000942: Strack traces can be unreadable due to missing foreground colour

ID	Project	Category	View Status	Date Submitted	Last Update
0000942	Xdebug	Uncategorized	public	2013-04-14 09:03	2021-03-17 08:54

Reporter	kAlvaro	Assigned To
Priority	normal	Severity	feature	Reproducibility	always
Status	resolved	Resolution	won't fix
Product Version	2.1.3

Summary	0000942: Strack traces can be unreadable due to missing foreground colour
Description	Strack traces set background colours but not foreground colours. That often makes the text barely unreadable, depending on what colours are set in the site's CSS.
Steps To Reproduce	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head><title></title> <style type="text/css"><!-- body{ color: #FF8204; background-color: black; } --></style> </head> <body> <h1>Unreadable stack trace</h1> <?php error_reporting(E_ALL); ini_set('display_errors', true); $foo++; ?> </div> </body> </html>
Tags	No tags attached.

Operating System
PHP Version	5.3.6

derick 2013-05-18 21:33 administrator ~0002474	Is there any reason why you can't set specific CSS classes on "xdebug-error"? All xdebug output has that.

kAlvaro 2013-05-22 15:11 reporter ~0002487	Sorry, I'm not sure whether you're stating that there's no need to fix the issue or just proposing a workaround. Of course, CSS allows to write custom code to override the default styles provided by Xdebug—I didn't mention this workaround because I assumed I was obvious. Other than that, if I'm supposed to style the stack traces myself I'd prefer to obtain bare HTML from Xdebug so I'm not forced to write CSS just to undo hard-coded styles. But I'd expect Xdebug to be a self-complete tool that allows standalone usage out of the box. It's great if further tweaking is allowed, but it shouldn't be mandatory. If built-in styles are provided, shouldn't they "just work"?