Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First of all, when checking for bugs like this (better yet, <strong>always!</strong>) validate your markup and CSS to be sure you're working on standard code. If not, you <em>will</em> have problems.</p> <p>A quick check on your markup throws 23 errors! <a href="http://validator.w3.org/check?uri=http%3A%2F%2Fbjmarine.net%2Fsamples.htm&amp;charset=%28detect+automatically%29&amp;doctype=Inline&amp;group=0" rel="nofollow noreferrer">http://validator.w3.org/check?uri=http%3A%2F%2Fbjmarine.net%2Fsamples.htm&amp;charset=%28detect+automatically%29&amp;doctype=Inline&amp;group=0</a></p> <p>Granted, most of them are from the HEAD section, but there are a couple in the body - solve those, then try again.</p> <p>Next: even with buggy markup, common sense tells you scrolling down and up shouldn't affect the rendering. That <strong>is</strong> a IE bug, for sure, so no question you'll have to change your code to solve it.</p> <p>So:</p> <ul> <li><p>You have invalid markup - don't expect quirks mode to interpret what you <em>meant</em>. Solve those before trying anything else (for example, UL can't be empty)</p></li> <li><p>Older versions of IE don't like the '>' CSS selector. Get rid of it and use classes instead.</p></li> <li><p>If you want to display something inline and with a specific height and width, use the <code>display: inline-block</code> rule, that's the correct option instead of just <code>display: block</code>.</p></li> <li><p>You have negative margins. That's not recommended at all. You usually have <em>much</em> better ways to solve it.</p></li> </ul> <p>As you can see, many things may be triggering that bug. Solve all of them (which you should do even if no bugs were present) and try again.</p> <p>If you're still getting it, consider refactoring your markup - we can find workarounds many times, but sometimes we have to adapt (we just <em>can't</em> fix IE bugs remotely...)</p>
    singulars
    1. This table or related slice is empty.
    1. POWhy is moving an element out of and back into the viewport affecting it?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSeb
    1. USSeb
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 because there are a lot of things that are odd about the structure of the code, it's always best to try to stick to standards-compliance when you can (and you can here).
      singulars
      1. PO
      1. USJasonWyatt
    2. COThanks for the input and yes I know I should validate more and such but when it works in all new browsers including the still average IE8 reality checks in and I have to move on if I want to keep my job. Worrying about standards for the browsers that are least compliant does seem a little bit counter intuitive in a funny way.
      singulars
      1. PO
      1. USDenis Hoctor
    3. CODenis, I couldn't DISagree more with you... standards should be preserved absolutely every time. That's what will ensure it'll work in new browsers, plus anyone maintaining your code (you now, others later) will find it much easier to do so. Also, just to name an example, how should `<UL></UL>` (invalid, as it has no children) be displayed? Since it's not standard, every browser will render it as it wants - being avoidable, I don't see why anyone would code out of the standards ever.
      singulars
      1. PO
      1. USSeb
 

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