[Bug 6381] New: Media=screen stops any CSS styles added to printing

[email protected]
Newsgroups gmane.comp.cms.xaraya.bugs
Message-ID <[email protected]>
http://bugs.xaraya.com/show_bug.cgi?id=6381

           Summary: Media=screen stops any CSS styles added to printing
           Product: App - Themes
           Version: unspecified
          Platform: All
               URL: http://themes.xaraya.com/?theme=Xaraya_Classic
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3 - Standard
         Component: Xaraya_Classic
        AssignedTo: [email protected]
        ReportedBy: [email protected]
         QAContact: [email protected]


User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.10)
Gecko/2009050804 Mandriva Firefox/3.0.10
Build Identifier: 

Xaraya_Classic and I guess other themes too, load styles with "media=screen".
These styles are not loaded for printing at all. Basically there is no style
for printing at all.

In most cases, this is not what the users want, in my opinion. Normally I would
load all styles for media="all", and customize a few rules (colors, layout,
hide blocks) with one single media="print" loaded extra CSS file. That's easier
than starting everything from scratch for the print media. (And other possible
media are not mentioned yet, but I think it's easier to customize main styles
than create one from scratch.)

Note, that media attribute default value differs based on the method the style
is included (e.g. inline, link, ..). 



Reproducible: Always

Steps to Reproduce:
1. Press "Print preview"
2.
3.

Actual Results:  
No styles for printing at all.

Expected Results:  
Add the site's own styles, and let site makers create an extra CSS file for
printing rules. For now, changing all media="screen" to media="all" would help.


-- 
Configure bugmail: http://bugs.xaraya.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

---- ** IMPORTANT ** READ BELOW ** ----
[Clip Me Start]
--------------------------------------------------------------------------
If you wish, you can reply to this message directly **however**, make sure
to use the "Reply To All" feature of your client **and** ensure that the 
bug specifier is in the subject (ie: [Bug ####]). Also, you _MUST_ have 
you're From or Reply-To address set to the same address you use to log
into your bugzilla account or your reply will not be attached to the bug.
--------------------------------------------------------------------------
[Clip Me End]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.