href url with /Ad blocking images

RESOLVED INVALID

Status

SeaMonkey
General
--
major
RESOLVED INVALID
15 years ago
13 years ago

People

(Reporter: Mike Odom, Unassigned)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529

On Netflix.com I'm unable to see the "rent" buttons. I narrowed it down to the
href tag having a /Ad string on it.

Their URL: 
<a onClick='rbflip("btn60002360-30-rent-1");'
href="http://www.netflix.com/AddToQueue?movieid=60002360&trkid=10472"><img
src="http://a408.g.akamai.net/f/408/1284/24h/image.netflix.com/NetFlix_Assets/buttons/rent/rent_d30_s0_v1.gif"
name="btn60002360-30-rent-1" width=65 height=16 vspace=2 border=0 alt="Rent"></a>

It's the href="http://www.netflix.com/AddToQueue .... Although only the
href="http://www.netflix.com/Ad is needed to reproduce this.



Reproducible: Always

Steps to Reproduce:
This simple code will do it, change the /Ad to /A or /Aalkjerahwer and it'll
work. But /Ad isn't working.
<a href="http://www.google.com/Ad">
<img src="http://www.google.com/images/logo.gif">
</a>

I trashed my Mozilla application folder, reinstalled 1.4 and tried a new profile
just to make sure it wasn't any of my ad blocking settings.
Actual Results:  
The image and link were not displayed

Expected Results:  
It should have displayed the image

Comment 1

15 years ago
do you have installed any kind of firewall, proxy or anything like that?
(Reporter)

Comment 2

15 years ago
My apologies. It was something inside of userContent.css that I had put in there
many moons ago.
A:link[HREF*="/ad"] IMG { display: none ! important }
Apparently switching to a new user did not remove this data.

Marking bug as INVALID.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → INVALID
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.