Lock frame scroll

top.window.frames['mainFrame'].scrolling is undefined.

I'd like to lock temporarly on Event a frame scroll.

How could I obtain such a result ?

I've just tried :
top.window.frames['mainMainFrame'].setAttribute("scrolling","no");

But, Mozilla Javascript Consol says :
top.window.frames.mainMainFrame.setAttribute is not a function.

Whereas top.window.frames['mainMainFrame'] is efficiently an [Object Window].

Assuming the ID on your <FRAME> is mainMainFrame, try this:

When I do this :


returns auto (the right original value) and no but, the scroll bar is still enabled.
(idem with : top.window.document.getElementById("mainFrame").setAttribute("scrolling","NO");)

Has nobody the solution to that problem ?

It works in Firefox 1.5 but not in Firefox 1.0.7. What version of Mozilla are you using?

I usally work with Firefox/1.0.7 AND Internet Explorer 6.0.

Actually, I'd like it to disable scroll bar with I.E. (users of my intranet app desperatly mainly use it).

I once again say: Don't try to control a browsers behaviour!
If your app doesn't work if a frame can scroll, make is so it DOES work.

What if I opened the frame in a seperate window?

Or in Lynx?

Sites like that only make me hit the 'disable javascript' button in my browser.

That kind of comment really brings a lot to the debate...

Ok, more clearly explained:

The reason you're having trouble getting different browsers to do this, is because it's not a standard function.
If it was, you wouldn't be mucking about in Javascript, you would simply set the (hypothetical) HTML 'noscroll' attribute (or the CSS equivalent, if you were wise).
But that attribute doesn't exist. It's not in HTML, because HTML defines what the different sections of the document represent, and it's not in CSS, because CSS defines how something is displayed, and if you want a part not to display, to set it to HIDDEN, you don't scroll it away, lock the scrollbar and throw away the key (metaphorically speaking).
So people who wanted weird things started mucking about in javascript, then Microsoft started mucking about in javascript, etc, resulting in endless different versions of the aforementioned scripting language, with tons of functions only supported in browser X provided you have version 3.14.1.5.9.2.65.4.etcera.

Javascript is great for 'smart' forms, for the rest, use CSS.

Oh, and don't get me started on CSS support on IE.
But then, people using IE have simply failed their drivers licence for the information highway.

I'll throw my two cents in here.

First, Itsacon, I love that line: people using IE have simply failed their drivers licence for the information highway.

I think the moral issue here lies with the use of the application... Public websites should NOT try to control a browser's behaviour... I fully agree with Itsacon here.

However, if it's an internal application for a company's internal website/intranet, there may be a reason to do stuff that may be deemed naughty otherwise. Plus, if your company standard is [*cringe*] Internet Explorer in a Windows environment, it may be excusable if your site/page design is tailered more for IE. Why would you bother worrying about Firefox or Safari?

Overall, however, I believe standard webdesign should be the front-most concern no matter where you're developing; however, if you need to let a few things slip, that should be alright.

In direct relation to the question -- not a rant based on Itsacon's position () -- Jackot, you've pointed out that this is for internal use.

I still raise the question though, if you disable scrollbars, what happens if the content flows off the screen?

Itsacon, it sounds like you don't like JavaScript much. IE doesn't support JavaScript. It has JScript which is a clone of JavaScript with a few changes.

The scrolling attribute of frame elements is included in HTML 4. In general the values of HTML attributes can be changed via the DOM, however, there are some attributes in each browser that haven't been given that functionality. When accessed via the DOM X/HTML attributes are referred to as properties.

Setting the scrolling property of frames dynamically works in Firefox 1.5 (Mozilla 1.8) but not in Firefox 1.0.7 (Mozilla 1.7). It works in Opera 7.23+ but does not seem to work in IE6. Only Firefox 1.5 (Mozilla 1.8) seems to allow disabling the scrollbar of frame elements via the CSS overflow property.
Note: I only tested these things on Windows browsers.


I agree.

Actually, I'm not that much against J(ava)Script.

I just hate it when people use it to limit a users abilities, when it's only a hindrance to most people. Simple example: A lot of sites use javascript to keep people from right-clicking images to save them. Why? Any decent browser can deactivate javascript to get the image anyway (In Opera, there are actually settings on how much you let javascript do in general), or you can simply grab it using wget.

There are plenty of good uses for JavaScript however, I've used itplenty of times:

• Form validation. It's great to show a popup when people enter invalid entries in a form. Of course you still need to check the input in the following page (PHP or something like that), in case people disable javascript, but adding the JS check as well can save a user valuable time submitting and reloading the page.
• Smart forms. I have plenty of forms where fields are re-populated based on the choices made in the same form. When done right, using the proper DOM attributes, this works on pretty much all browsers (with exceptions such as Lynx of course), and can, again, save a user a lot of submitting and reloading, by eliminating the need to make every step a new form.
• Programs. JavaScript is a nigh-complete programming language, and you can do some amazing stuff with it, up to and including image-editing. You should ask Icon sometime.

There are undoubtly plenty of other good uses for JS, but limiting a user's abilities to use his own browser is simply not one of them, if you ask me.

Explaining why I want to lock a scrollbar would be busy but I'm gonna try to :

I open a pdf document inside an iframe which temporarily covers totality the navigator window so that the user cannot activate another link of the main window before having closed the div which includes the iframe.

As the content of the main window is large, it must contain a scroll bar.

Man must know that several pages of my Intranet site are succeptible to be simutaneously opened (in order to compare MySQL datas), that's why it is almost inevitable to limit the number of blank-targeted links and use temporary iframes (keeping many user-defined informations on main-window configuration in a simple way)...

I'm not sure on being clear but, I would have needed such a configuration under IE5+.