Hi!
how implement a print version of the css
@jlukic A very easy and cool implementation would be adding "printable" and "non printable" semantics for elements :) Catch them with print media and voila, you're good!
But there is nothing speaking against doing a real print.css too :)
Hint: Printable forces display: block/inline and opacity:1, non printable forces display:none and opacity:0
@jlukic is there any ETA in which version this would be implemented?
+1
This missing feature is a major one, in my opinion, as most of my projects require the very... very handy print CSS rules from Bootstrap which I use at the moment.
I think the best way to accomplish this would be if every components would implement their own print rules, then add some extra general rules, like in Bootstrap's visible-print-* and hidden-print, etc. (those are trivial). It seems quite trivial, sure, but it should not be left to the user or web integrator to monkey patch Semantic UI this way.
Where this gets complicated is deciding "what grid size applies when printing?", combined with the fact that Chrome screws up the viewport size when printing (see http://crbug.com/273306).
Deciding page flow when printing is usually in my experience, also a pretty manual job.
+1 to @yanickrochon comments, needs to be a priority. I prefer pages to "just print properly". Yes, you'll also need print helper classes to adjust things, such as hiding the top menu.
I really wish frameworks like Semantic, Bootstrap, Foundation, etc. would be "print first". It seems like the mobile stuff has been worked out now so we don't need to accommodate "mobile first" (media queries work). Due to the Chrome bug mentioned above, it's difficult to get printing to work with responsive designs. (sigh)
As for grid size, I prefer the tablet size. Certainly not mobile. I'd say pick something and provide good defaults. Everyone will always need to make adjustments..
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs. Thank you for your contributions.
Bump (due to stale bot). Still a valid feature request.
Would love that feature too
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs. Thank you for your contributions.
ping
ping
pong
Most helpful comment
ping