Re: [fossil-users] style.css served with on settings conflict

2018-06-07 Thread Warren Young
On Jun 7, 2018, at 6:58 PM, Andy Goth  wrote:
> 
> how does the error logger know that its output will wind up inside CSS?

Is there any kind of “context” object that gets passed through the page 
rendering logic?  If so, the high-level code that generates the CSS can declare 
that the final destination is CSS, cluing the code that builds the error string 
into putting it inside a C-style block comment, or suppressing it entirely.

If not, then the context can be global.  It’s ugly, but it really is global 
context for that particular Fossil child/CGI handler.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] style.css served with on settings conflict

2018-06-07 Thread Andy Goth

On 06/07/18 19:55, Warren Young wrote:

The error prepended to web pages served by Fossil on settings conflicts is 
being prepended to the style.css file, causing the CSS to be considered invalid 
by Chrome, at least.

This should be done on HTML output only.


I had this same problem back when we were having trouble with read-only 
repositories on Windows.  Richard fixed it by reworking how SQLite deals 
with Windows virus scanners lying about file access, but we never 
actually changed the error logger.


In the case of CSS, errors can still be reported, but they have to be 
made to look like comments.  Text prepended to HTML tends to be 
tolerated as-is though, so only CSS needs a fix.  Trouble is, how does 
the error logger know that its output will wind up inside CSS?


--
Andy Goth | 
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] style.css served with on settings conflict

2018-06-07 Thread Warren Young
The error prepended to web pages served by Fossil on settings conflicts is 
being prepended to the style.css file, causing the CSS to be considered invalid 
by Chrome, at least.

This should be done on HTML output only.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users