April
18
July
30
New Edge browser crashes if do search on address bar
UPDATE: Microsoft has fix this in the latest release, 84.0.522.59
The new Edge – version 84.0.522.49 – will crash if you do a search on address bar and have google.com as your search engine.
I changed to Bing as search engine and everything is fine.
I have reported this to Microsoft Edge team as feedback
NOTE: I am wondering if Microsoft did this on purpose 🙂
January
10
SharePoint Screen Apps
SharePoint Screen Apps are content editor web parts that connect to a text file that is really an html file.
That text file includes css & js to load up jquery, react, angularjs, bootstrap, and some special function used to assist in calling SharePoint Rest APIs.
This allows for any jquery (datatable.net, jslider, etc.) to be used on the page.
I am working on book that will detail this and have a CD of examples
October
23
SharePoint 2013 On-Site vs Office 365 Cloud
So you have been tasked with choosing between in on-site vs cloud versions of SharePoint.
You have another choice and that is to do both also known as hybrid.
SharePoint 2013 features are the same on-site and in the cloud.
A Forrester Research Inc. survey of IT decision makers shows:
- 62% (82% in 2010) plan to deploy SharePoint 2013 on-premises
- 8% (4% in 2010) will do so in a Microsoft datacenter
- 26% (5% in 2010) will deploy SharePoint in a hybrid mode, both on-premises and cloud
While that shows a clear majority plan to run SharePoint in-house, that number is down from 2010.
Metalogix Software Corporate Survey had similar findings, showing
- 55% intend to continue running SharePoint entirely in-house
- 10% plan to run it purely in the cloud.
- 35% are planning hybrid SharePoint implementations.
Let us look at some business rules that would slant you one way or the other.
| Business Rule | On-Site | Cloud |
| Company does not want information outside the premises | X | |
| Company has users over across multiple continent | X | |
| Company is involved in a lot of legal battles | X | |
| Company needs to interact with external clients | X | |
| Company wants to be use SharePoint as Order Entry System | X | |
| Company does not have IT Operational department personal to support SharePoint long term | X | |
| Need to connect SharePoint to on-site systems | X | |
| Company is moving everything to the “Cloud” | X | |
| Company does not have financial resources to take on yearly cloud membership fees | X | |
| Company want to increase their mobile access | X |
Security issues have caused a lot of companies to avoid the cloud. With all the security breaches in the news a lot these days, it easy to see why companies IT Security officers do want anything to do with any cloud based system.
The promise of reduced cost have a lot of company thinking about moving to the cloud, doing research on cloud benefits, or taking the plunge and moving to the cloud.
Comfort level with what you know has caused a lot to go with on-site implementation.
Areas which I have seen that influence the direction are: Comfort, Cost & Legal.
– If a company already has SharePoint on-site and they are upgrading to 2013, they tend to keep it on-site.
– If a company is looking to reduce infrastructure cost, they tend to go with a cloud based solution.
– If a company’s legal department want to control their intellectual properties and assets, they tend to keep it on-site
July
6
X-UA-Compatible meta tag
The X-UA-Compatible meta tag allows web authors to choose what version of Internet Explorer the page should be rendered as. IE11+ have changes to these modes. See IE11 note below. The IE Technical Preview, the version that will be released after IE 11, will only honor X-UA-Compatible meta tag in certain circumstances. See IE Technical Preview note below.
Here are your options:
- “IE=edge”
- “IE=10”
- “IE=EmulateIE10”
- “IE=9”
- “IE=EmulateIE9
- “IE=8”
- “IE=EmulateIE8”
- “IE=7”
- “IE=EmulateIE7”
- “IE=5”
To attempt to understand what each means here are definitions provided by Microsoft:
Internet Explorer supports a number of document compatibility modes that enable different features and can affect the way content is displayed:
- IE10 mode provides the highest support available for established and emerging industry standards, including the HTML5, CSS3 and others.
- IE9 mode provides the highest support available for established and emerging industry standards, including the HTML5 (Working Draft), W3C Cascading Style Sheets Level 3 Specification (Working Draft), Scalable Vector Graphics (SVG) 1.0 Specification, and others. [Editor Note: IE 9 does not support CSS3 animations].
- IE8 mode supports many established standards, including the W3C Cascading Style Sheets Level 2.1 Specification and the W3C Selectors API; it also provides limited support for the W3C Cascading Style Sheets Level 3 Specification (Working Draft) and other emerging standards.
- IE7 mode renders content as if it were displayed in standards mode by Internet Explorer 7, whether or not the page contains a directive.
- Emulate IE9 mode tells Internet Explorer to use the directive to determine how to render content. Standards mode directives are displayed in IE9 mode and quirks mode directives are displayed in IE5 mode. Unlike IE9 mode, Emulate IE9 mode respects the directive.
- Emulate IE8 mode tells Internet Explorer to use the directive to determine how to render content. Standards mode directives are displayed in IE8 mode and quirks mode directives are displayed in IE5 mode. Unlike IE8 mode, Emulate IE8 mode respects the directive.
- Emulate IE7 mode tells Internet Explorer to use the directive to determine how to render content. Standards mode directives are displayed in Internet Explorer 7 standards mode and quirks mode directives are displayed in IE5 mode. Unlike IE7 mode, Emulate IE7 mode respects the directive. For many web sites, this is the preferred compatibility mode.
- IE5 mode renders content as if it were displayed in quirks mode by Internet Explorer 7, which is very similar to the way content was displayed in Microsoft Internet Explorer 5.
- Edge mode tells Internet Explorer to display content in the highest mode available. With Internet Explorer 9, this is equivalent to IE9 mode. If a future release of Internet Explorer supported a higher compatibility mode, pages set to edge mode would appear in the highest mode supported by that version. Those same pages would still appear in IE9 mode when viewed with Internet Explorer 9.
NOTE: As of Internet Explorer 10, quirks mode behaves differently than it did in earlier versions of the browser. In Windows Internet Explorer 9 and earlier versions, quirks mode restricted the webpage to the features supported by Microsoft Internet Explorer 5.5. In Internet Explorer 10, quirks mode conforms to the differences specified in the HTML5 specification.
IE 11
From Microsoft (here):
Starting with IE11, edge mode is the preferred document mode; it represents the highest support for modern standards available to the browser.
Use the HTML5 document type declaration to enable edge mode:
<!doctype html>
Edge mode was introduced in Internet Explorer 8 and has been available in each subsequent release. Note that the features supported by edge mode are limited to those supported by the specific version of the browser rendering the content.
Starting with IE11, document modes are deprecated and should no longer be used, except on a temporary basis. Make sure to update sites that rely on legacy features and document modes to reflect modern standards.
If you must target a specific document mode so that your site functions while you rework it to support modern standards and features, be aware that you’re using a transitional feature, one that may not be available in future versions.
If you currently use the x-ua-compatible header to target a legacy document mode, it’s possible your site won’t reflect the best experience available with IE11.
IE Technical Preview
Information on X-UA-Compatible meta tag for the next version of IE. From Microsoft(here):
Introducing the “living” Edge document mode
As we announced in August 2013, we are deprecating document modes as of IE11. With our latest platform updates, the need for legacy document modes is primarily limited to Enterprise legacy web apps. With new architectural changes, these legacy document modes will be isolated from changes in the “living” Edge mode, which will help to guarantee a much higher level of compatibility for customers who depend on those modes and help us move even faster on improvements in Edge. The next major version of IE will still honor document modes served by intranet sites, sites on the Compatibility View list, and when used with Enterprise Mode only.
Public Internet sites will be rendered with the new Edge mode platform (ignoring X-UA-Compatible). It is our goal that Edge is the “living” document mode from here out and no further document modes will be introduced going forward.
Chrome=1 Info for IE
There is also chrome=1 that you can use or use together with one of the above options, EX: <meta http-equiv="X-UA-Compatible" content="IE=Edge,chrome=1"> chrome=1 is for Google’s Chrome Frame which is defined as:
Google Chrome Frame is an open source browser plug-in. Users who have the plug-in installed have access to Google Chrome’s open web technologies and speedy JavaScript engine when they open pages in the browser.
Google Chrome Frame seamlessly enhances your browsing experience in Internet Explorer. It displays Google Chrome Frame enabled sites using Google Chrome’s rendering technology, giving you access to the latest HTML5 features as well as Google Chrome’s performance and security features without in any way interrupting your usual browser usage.
When Google Chrome Frame is installed, the web just gets better without you having to think about it.
But for that plug-in to work you must use chrome=1 in the X-UA-Compatible meta tag.
More info on Chrome Frame can be found here.
Note: Google Chrome Frame was retired on February 25, 2014. More info can be found here. Thank You @mck for the link.
Validation:
HTML5:
The page will validate using the W3 Validator only when using <meta http-equiv="X-UA-Compatible" content="IE=Edge">. For other values it will throw the error: A meta element with an http-equiv attribute whose value is X-UA-Compatible must have a content attribute with the value IE=edge. In other words, if you have IE=edge,chrome=1 it will not validate. I ignore this error completely as modern browsers simply ignore this line of code.