Does Firefox (current version 28) still block iFrames by default?

[John Corliss]

In the past, I've tweaked settings so that Firefox blocks IFrames. I did
this by following these instructions:
________________________________________________________________________
To block IFRAMEs, you must create a file named userContent.css. Put
userContent.css in the Chrome folder, which is inside the user profile
folder. (The user profile folder is the folder that contains the
prefs.js file and possibly a user.js file.) Inside the userContent.css
file, on its own line, put the following:

IFRAME {display: none !important;}
________________________________________________________________________

However, now I notice that there isn't a Chrome folder by default any
longer. I would rather avoid all this stuff if somebody would tell me
whether or not Firefox still blocks IFrames by default. Does it?

TIA

--
John Corliss

[Ralph Fox]

My Firefox has never blocked iframes by default. Not through all the
versions of Firefox I have used. On this computer that covers release
versions 3.6 through to 28.0.

test: http://www.w3schools.com/tags/tryit.asp?filename=tryhtml_iframe


--
Kind regards
Ralph

[Millwood]

The extension stylish is, IMHO, a much better way to introduce css
changes.

https://addons.mozilla.org/en-US/firefox/addon/stylish/?src=search

[Chris Ilias]

As Ralf said, Firefox never blocked iframes by default. "By default"
means that you don't have to add or set anything. That's why the
userContent.css script has to be added.

Regarding the chrome folder, Firefox still supports it; it just doesn't
get created automatically. You need to create the folder, and the
userContent.css file in it.

--
Chris Ilias <http://ilias.ca>
Mailing list/Newsgroup moderator

[John Corliss]

Sorry, I was in a hurry yesterday and left out a critical word in my
question. The question should be:

Does Firefox (current version 28) still block *third party* iFrames by
default?

TIA again.

--
John Corliss

[John Corliss]

Thanks Chris. And I really meant to say "third party iframes". Sorry.
Guess I'm still looking for a way to do that. The setting I mentioned
above blocks all IFrames, and that's probably caused me problems in the
past.

--
John Corliss

[Ralph Fox]

Firefox 3.6 did not block third-party iframes by default. I have just
tested it.


For a test, I went to http://www.vodafone.com.au/help/devices/ota-settings
The text starting with "Mobile Phone · Select Mobile Phone Manufacturer"
is in a third-party iframe from wdsglobal.com. Vodafone Australia
outsources its Over-The-Air (OTA) set-up service to WDS, like a
number of other mobile telcos do.

There are other sites that outsource credit-card payments to a secure
payment provider, with the credit card form in a 3rd-party iframe.
I don't believe my Firefox has ever blocked third-party iframes by
default, or otherwise these sites would not have been able to show
the credit card form.

For another test, I went to http://css-tricks.com/examples/iFrameResize/crossdomain.php
The grey box below the paragraph "The block below [...] resize to
adjust" is a third-party iframe from digwp.com.



--
Kind regards
Ralph

[John Corliss]

Ralph Fox wrote:
> On Wed, 02 Apr 2014 23:25:03 -0700, John Corliss wrote:
>
>> John Corliss wrote:
>>> In the past, I've tweaked settings so that Firefox blocks IFrames. I did
>>> this by following these instructions:
>>> ________________________________________________________________________
>>> To block IFRAMEs, you must create a file named userContent.css. Put
>>> userContent.css in the Chrome folder, which is inside the user profile
>>> folder. (The user profile folder is the folder that contains the
>>> prefs.js file and possibly a user.js file.) Inside the userContent.css
>>> file, on its own line, put the following:
>>>
>>> IFRAME {display: none !important;}
>>> ________________________________________________________________________
>>>
>>> However, now I notice that there isn't a Chrome folder by default any
>>> longer. I would rather avoid all this stuff if somebody would tell me
>>> whether or not Firefox still blocks IFrames by default. Does it?
>>>
>>> TIA
>>
>> Sorry, I was in a hurry yesterday and left out a critical word in my
>> question. The question should be:
>>
>> Does Firefox (current version 28) still block *third party* iFrames by
>> default?
>
>
> Firefox 3.6 did not block third-party iframes by default. I have just
> tested it.

No, they started doing it in a much more recent version if what I read
on the internet was correct. However, try as I might I've been unable to
relocate that reference.

> For a test, I went to http://www.vodafone.com.au/help/devices/ota-settings
> The text starting with "Mobile Phone · Select Mobile Phone Manufacturer"
> is in a third-party iframe from wdsglobal.com. Vodafone Australia
> outsources its Over-The-Air (OTA) set-up service to WDS, like a
> number of other mobile telcos do.
>
> There are other sites that outsource credit-card payments to a secure
> payment provider, with the credit card form in a 3rd-party iframe.
> I don't believe my Firefox has ever blocked third-party iframes by
> default, or otherwise these sites would not have been able to show
> the credit card form.

Well, that wouldn't break my heart because I don't use credit cards.

> For another test, I went to http://css-tricks.com/examples/iFrameResize/crossdomain.php
> The grey box below the paragraph "The block below [...] resize to
> adjust" is a third-party iframe from digwp.com.

Well, thanks for your input. I'll keep looking for a way though.

--
John Corliss