Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As <a href="https://stackoverflow.com/questions/15416557/css-print-stylesheet-hide-everything-except-specific-image-show-that-full-page#comment-21799343">Diodeus notes in the comments</a>, the visibility of any given element doesn't matter if its parent is not displaying — in fact in many browsers the resource won't even be loaded.</p> <p>I would propose these changes:</p> <pre><code>* { background: none !important; direction: ltr !important; display: none !important; font-size: 0 !important; height: 0 !important; line-height:-9999 !important; margin: 0 !important; padding: 0 !important; position: static !important; text-indent:-9999em !important; width: 0 !important; white-space:normal !important; } html, body, div, #specificimage { display: block !important; } #specificimage { left: 0 !important; position: fixed !important; top: 0 !important; width: 100% !important; } </code></pre> <p>The <code>*</code> rule is pretty heavy, but makes sure that:</p> <ul> <li>The size (or number of pages, because of a page structure taller than one page) will not be influenced by metrics, which is influenced by border, height, margin, width;</li> <li>Text immediately inside a <code>div</code> is not visible: negative text indent, forced direction of left to right, plus zero font-size and forced wrapping via white-space: normal mean it will be hidden out to the left and won't extend the width. a negative line-height means it will be hidden off to the top too, and won't extend the height (or number of pages) if it's extremely long.</li> <li>Position: static means left, right, top or bottom won't extend the page canvas more than it needs.</li> <li>The important rule is there because whatever rules giving any of these properties to your elements in the first place will always be stronger. Without making assumptions about the document structure, we have to apply this override. If you need to make this trump more specific class and selector-based rules with <code>!important</code> specified, you can append <code>:nth-child(n)</code> to the asterisk any number of times, but this won't help against inline styles or rules with ID selectors that also have importance toggled.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POCSS Print Stylesheet: hide everything except specific image, show that full-page
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USBarney
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCSS Print Stylesheet: hide everything except specific image, show that full-page
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThank you, that's very close! I needed to add `height: auto` to the #specificimage rule, and it printed great in Firefox 19, IE 9, and Chrome 24 -- Safari only prints a very tiny box near the top left of the page. I'll keep trying to tweak. Thanks again.
      singulars
      1. PO
      1. USD. Richelieu
    2. COI seem to remember facing near enough the same problem (Safari not playing nice) when designing a page to print a voucher about 4 years ago... Will do some digging if I get the time.
      singulars
      1. PO
      1. USBarney
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload