Rob Kendrick  wrote on 19 Feb:

> On Mon, Feb 19, 2018 at 03:46:41PM +0000, Jim Nagel wrote:
>>   - Netsurf displays the pages served up via Webjames perfectly,
>> except that it is NOT obeying the stylesheet (which is  /2018.css )
>> even though the Webjames log records a GET success for the CSS file
>> just as it did for the logo and paper and favicon.
>>   - Yet when Netsurf fetches the identical page from my ISP's server,
>> it DOES obey the CSS.

> Complete guess: is your CSS source file set to the CSS type, or plain
> text type?  I'm not sure how NetSurf reacts to CSS files served with an
> appropriate Content-Type header.

Thanks, Rob.  Sorry for delayed response.  (I think I covered the 
point elsewhere in the thread, though.)

Yes, the source file was called !2018.css but its RiscOS filetype was 
still text.  I changed the filetype to CSS and Netsurf is now happy.

I can't quite get my head around this (not that it matters, since 
things are working now):

 - The distant server (probably running on Linux) does not care about 
RiscOS filetypes and Netsurf correctly displays pages from there when 
my !2018.css has RiscOS filetype as text

 - The local development server (Webjames) does a successful GET of 
!2018.css whatever its RiscOS filetype, but Netsurf does not display 
pages correctly when !2018.css is Ro-filetyped as text, and *does* 
display them correctly when !2018.css Ro-filetype is changed to CSS.


-- 
Jim Nagel                             www.archivemag.co.uk
|| See you at the show?   www.riscos-swshow.co.uk   Feb 24

Reply via email to