Here’s a little nugget I came across, on SharePoint 2010 and 2013 (including O365), and was exceptionally frustrated with. There’s a difference between IsDlg and isdlg. See it? Case sensitivity. Come to find out that means the world to SharePoint.
I was tasked to setup a basic Page Viewer web part to consume a page from another web. Simple enough. I threw the URL into the web part, including IsDlg=1, and blamo, I got my page. However, I couldn’t scroll the web part. The page I was using was longer than the web part, which would normally cause the page to scroll, but alas, not in this web part.
Enter the IsDlg parameter. Don’t know what IsDlg is? It’s a little query string parameter that SharePoint uses to hide elements on your page using CSS. Have you noticed that if you enable the dialog on a list, and the forms then appear in the dialog window, that the header is missing? The left nav too?
It’s the same page as if you didn’t use the dialog setting, Microsoft isn’t crazy enough to have two versions of a page that does the same thing. Instead when the IsDlg parameter is sent to the page as a parameter in the query string, it hides everything on the page with a CSS class of s4-notdlg.
Here’s what the URL may look like:
/sites/lozzi/Lists/Events/DispForm.aspx?ID=4&IsDlg=1
Note the IsDlg=1 at the end. I’m a big fan in questioning everything, so let’s try it out for ourselves.
Go to a display form of a list item, which is not in a dialog.
and add &IsDlg=1 (case sensitive) to the end of the URL, hit enter.
See how we lost the top header and left nav? Looks like the dialog up above, right? Pretty cool eh? So, as you may be thinking, “this is awesome, I can use this in the page viewer web part too”. You would be correct in your thinking! Here’s where things get a little fishy.
When you use IsDlg (again case sensitive), SharePoint does NOT scroll the window if the window requires it. Again, give it a whirl. Take your window you used above, and resize it so it’s nice and small, put the Close button below the bottom of the window.
See? The close button is below the window, but there’s no scroll bars. If you change the IsDlg to isdlg, then you get a happier page.
Whew, there’s our trusty little scroll bar, now I can press Close.
Let’s dig deeper: core.js
Why is this happening? Well I dove into the JavaScript that handles it, in the core.js file, there are several lines of code which look similar to:
isdlg = (ajaxNavigate.get_search()).match(new RegExp("[?&]IsDlg=1"));
JavaScript is very case sensitive, so it’s actually, and quite specifically, looking for IsDlg, not isdlg. Weird right? So if you send the page IsDlg, SharePoint forces the size of the window and disables the scrolling. If you send isdlg, SharePoint does nothing with it except for hiding the CSS elements (as we discussed earlier). Your browser’s native capabilities kick in and scrolling occurs.
This is great for the dialog interface SharePoint is use to as they will size with the page. Now the user is scrolling the entire page and not just the page within the dialog. This is annoying for us if we want to use IsDlg feature elsewhere and we want to scroll just inside the web part. We have to use the isdlg option instead.
Oh yeah, I confirmed this occurs in Internet Explorer, FireFox and Chrome too ;)
‘Til next time, Happy SharePointing!