Image permissions
Today I thought I'll try out the 'accept images from originating server only' (although I already use adblock). I opened my Twitter page, and all the user profile pics were blocked. Found that they were coming from a0, a1, a2, a3.twimg.com Now the problem is that the image permissions window forces you to specify the full URL of each subdomain separately. Can we have wildcard support in a future release, eg always block *.doubleclick.net, or always allow *.twimg.com ? - The Law, in its majestic equality, forbids the rich, as well as the poor, to sleep under the bridges, to beg in the streets, and to steal bread. -- Anatole France - ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Image permissions
On 1/11/2010 12:14 AM, Rex wrote: Today I thought I'll try out the 'accept images from originating server only' (although I already use adblock). I opened my Twitter page, and all the user profile pics were blocked. Found that they were coming from a0, a1, a2, a3.twimg.com Now the problem is that the image permissions window forces you to specify the full URL of each subdomain separately. Can we have wildcard support in a future release, eg always block *.doubleclick.net, or always allow *.twimg.com ? This is bug #78104. See https://bugzilla.mozilla.org/show_bug.cgi?id=78104. -- David E. Ross http://www.rossde.com/ Go to Mozdev at http://www.mozdev.org/ for quick access to extensions for Firefox, Thunderbird, SeaMonkey, and other Mozilla-related applications. You can access Mozdev much more quickly than you can Mozilla Add-Ons. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Image permissions
David E. Ross wrote: On 1/11/2010 12:14 AM, Rex wrote: Today I thought I'll try out the 'accept images from originating server only' (although I already use adblock). I opened my Twitter page, and all the user profile pics were blocked. Found that they were coming from a0, a1, a2, a3.twimg.com Now the problem is that the image permissions window forces you to specify the full URL of each subdomain separately. Can we have wildcard support in a future release, eg always block *.doubleclick.net, or always allow *.twimg.com ? This is bug #78104. Seehttps://bugzilla.mozilla.org/show_bug.cgi?id=78104. Interesting Bug (I find it funny that the Bugzilla page shows 291 warnings using the HTML Validator extension) I'm finding so far the only two pages that appear to be correct is Mozilla's Home Page and my website. -- Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it http://www.phillipmjones.net http://www.vpea.org mailto:pjon...@kimbanet.com ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Image permissions
On 1/11/2010 10:03 AM, Phillip Jones wrote: David E. Ross wrote: On 1/11/2010 12:14 AM, Rex wrote: Today I thought I'll try out the 'accept images from originating server only' (although I already use adblock). I opened my Twitter page, and all the user profile pics were blocked. Found that they were coming from a0, a1, a2, a3.twimg.com Now the problem is that the image permissions window forces you to specify the full URL of each subdomain separately. Can we have wildcard support in a future release, eg always block *.doubleclick.net, or always allow *.twimg.com ? This is bug #78104. Seehttps://bugzilla.mozilla.org/show_bug.cgi?id=78104. Interesting Bug (I find it funny that the Bugzilla page shows 291 warnings using the HTML Validator extension) I'm finding so far the only two pages that appear to be correct is Mozilla's Home Page and my website. While the W3C validator reported 14 warnings (not 291) for the cited bug report, it did not find any HTML errors. -- David E. Ross http://www.rossde.com/ Go to Mozdev at http://www.mozdev.org/ for quick access to extensions for Firefox, Thunderbird, SeaMonkey, and other Mozilla-related applications. You can access Mozdev much more quickly than you can Mozilla Add-Ons. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Image permissions
Phillip Jones wrote: (I find it funny that the Bugzilla page shows 291 warnings using the HTML Validator extension) I'm finding so far the only two pages that appear to be correct is Mozilla's Home Page and my website. There are plenty of non-bozos out there: http://validator.w3.org/check?uri=http://www.clamwin.com/ http://validator.w3.org/check?uri=http://communitylinux.org http://validator.w3.org/check?uri=http://www.debian.org/ http://validator.w3.org/check?uri=http://fark.com http://validator.w3.org/check?uri=http://easyubuntu.freecontrib.org/ http://validator.w3.org/check?uri=http://www.gentoo.org/ http://validator.w3.org/check?uri=http://www.ghacks.net/2010/01/02/how-to-choose-a-linux-distribution-flow-chart/ http://validator.w3.org/check?uri=http://www.gnu.org/philosophy/right-to-read.html http://validator.w3.org/check?uri=http://www.ic3.gov/ http://validator.w3.org/check?uri=http://www.linuxcommand.org/man_pages/lsmod8.html http://validator.w3.org/check?uri=http://www.nerdkits.com/ http://validator.w3.org/check?uri=http://www.noooxml.org/irregularities http://validator.w3.org/check?uri=http://www.opera.com/support/mastering/kiosk/ http://validator.w3.org/check?uri=http://users.skynet.be/fa258499/extensions.html http://validator.w3.org/check?uri=http://www.skype.com/products/skypeout/rates/connection_fee.html http://validator.w3.org/check?uri=http://veecad.com/ http://validator.w3.org/check?uri=http://en.wikipedia.org/wiki/HTML ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Image permissions
David E. Ross wrote: On 1/11/2010 10:03 AM, Phillip Jones wrote: David E. Ross wrote: On 1/11/2010 12:14 AM, Rex wrote: Today I thought I'll try out the 'accept images from originating server only' (although I already use adblock). I opened my Twitter page, and all the user profile pics were blocked. Found that they were coming from a0, a1, a2, a3.twimg.com Now the problem is that the image permissions window forces you to specify the full URL of each subdomain separately. Can we have wildcard support in a future release, eg always block *.doubleclick.net, or always allow *.twimg.com ? This is bug #78104. Seehttps://bugzilla.mozilla.org/show_bug.cgi?id=78104. Interesting Bug (I find it funny that the Bugzilla page shows 291 warnings using the HTML Validator extension) I'm finding so far the only two pages that appear to be correct is Mozilla's Home Page and my website. While the W3C validator reported 14 warnings (not 291) for the cited bug report, it did not find any HTML errors. http://www.phillipmjones.net/Finderpicture002.png -- Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it http://www.phillipmjones.net http://www.vpea.org mailto:pjon...@kimbanet.com ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Image permissions
Phillip Jones wrote: David E. Ross wrote: On 1/11/2010 10:03 AM, Phillip Jones wrote: David E. Ross wrote: On 1/11/2010 12:14 AM, Rex wrote: Today I thought I'll try out the 'accept images from originating server only' (although I already use adblock). I opened my Twitter page, and all the user profile pics were blocked. Found that they were coming from a0, a1, a2, a3.twimg.com Now the problem is that the image permissions window forces you to specify the full URL of each subdomain separately. Can we have wildcard support in a future release, eg always block *.doubleclick.net, or always allow *.twimg.com ? This is bug #78104. Seehttps://bugzilla.mozilla.org/show_bug.cgi?id=78104. Interesting Bug (I find it funny that the Bugzilla page shows 291 warnings using the HTML Validator extension) I'm finding so far the only two pages that appear to be correct is Mozilla's Home Page and my website. While the W3C validator reported 14 warnings (not 291) for the cited bug report, it did not find any HTML errors. http://www.phillipmjones.net/Finderpicture002.png http://www.phillipmjones.net/SeaMonkeypicture001a.png http://www.phillipmjones.net/SeaMonkeypicture002a.png -- Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it http://www.phillipmjones.net http://www.vpea.org mailto:pjon...@kimbanet.com ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Image permissions
David E. Ross wrote: On 1/11/2010 12:14 AM, Rex wrote: Today I thought I'll try out the 'accept images from originating server only' (although I already use adblock). I opened my Twitter page, and all the user profile pics were blocked. Found that they were coming from a0, a1, a2, a3.twimg.com Now the problem is that the image permissions window forces you to specify the full URL of each subdomain separately. Can we have wildcard support in a future release, eg always block *.doubleclick.net, or always allow *.twimg.com ? This is bug #78104. Seehttps://bugzilla.mozilla.org/show_bug.cgi?id=78104. Wow, quite an old bug. But it seems to suggest adding AdBlock like features into Mozilla as the thread progresses. Instead of going into regexes, it would be nice to be just able to allow simple wildcards for permissible image servers. - Usenet is like a herd of performing elephants with diarrhea; massive, difficult to redirect, awe-inspiring, entertaining, and a source of mind boggling amounts of excrement when you least expect it. -- Gene Spafford,1992 - ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
