Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <h3>HTML</h3> <p>IE 9 and earlier (down to, I think, IE 4) can be identified using <a href="http://en.wikipedia.org/wiki/Conditional_comment" rel="nofollow noreferrer">conditional comments</a> in HTML.</p> <p>As <a href="https://stackoverflow.com/a/18739696/20578">@Jost noted</a>, you could use them to warn IE users on IE 8 and earlier, like this:</p> <pre><code>&lt;!--[if lte IE 8]&gt; BANNER HERE &lt;![endif]--&gt; </code></pre> <p>However, as IE 10 dropped support for these, you can't use them to identify non-IE browsers.</p> <h3>jQuery</h3> <p>jQuery used to include a browser detection module (<a href="http://api.jquery.com/jQuery.browser/" rel="nofollow noreferrer"><code>$.browser</code></a>), but <a href="http://jquery.com/upgrade-guide/1.9/#jquery-browser-removed" rel="nofollow noreferrer">it was removed in jQuery 1.9</a>. If you can use an earlier version of jQuery (e.g. <a href="http://blog.jquery.com/2012/11/13/jquery-1-8-3-released/" rel="nofollow noreferrer">1.8.3</a>) or the <a href="https://github.com/jquery/jquery-migrate/#readme" rel="nofollow noreferrer">jQuery Migrate plugin</a>, then you could use this to show the banner.</p> <pre><code>if ( !$.browser.msie || $.browser.version &lt; 9 ) { // Add banner to the page here. } </code></pre> <h3>Browser Detection in general</h3> <p>Please note that browser detection is difficult. New browsers are coming out all the time, so any browser support plugin can rapidly become out of date, as can the premise on which you base your warning messages. jQuery's browser detect was the most consistently maintained, and even they gave up on it in the end.</p> <p>These days, web developers are generally expected to write code that works cross-browser, and use feature-detection to deal with browsers that don't support the features they want to use.</p> <p>As you're working on a SharePoint site, presumably it's for internal company use, and the company is Microsoft-centric. It sounds like you're developing the site to work in IE, and ignoring other browsers during development.</p> <p>If you can reasonably expect most of your users to be on some version of IE, maybe the conditional comment warning is enough.</p>
    singulars
    1. This table or related slice is empty.
    1. POShow a message if the browser is not internet explorer 9 or greater
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USPaul D. Waite
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POShow a message if the browser is not internet explorer 9 or greater
      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. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    1. CODoes my Answer explain why i thought it might be easier to do it the other way round? *(refering to your comment on @Josts' deleted Answer)*
      singulars
      1. PO
      1. USMoritz Roessler
    2. COConditional comment are gone, `$.browser` is dropped, browsers detection is bad. Where is an answer to the actual question?
      singulars
      1. PO
      1. USPavlo
    3. CO@C5H8NNaO4: Yup - I can see that setting `display:none` is easier than adding the banner via JavaScript. However, I would note that when you do it that way round, then if the detection script fails, the user sees the warning. From what the OP says I think a false positive (showing the warning in a new browser) is worse than a false negative (not showing the warning in an old browser).
      singulars
      1. PO
      1. USPaul D. Waite
 

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