The Anchor Links do not work on a page viewed in firebird .6 click on them and nothing happens....double checked functionality in IE 6 and NS 7 works fine in those environments.

RESOLVED INVALID

Status

()

Firefox
General
RESOLVED INVALID
15 years ago
14 years ago

People

(Reporter: Ken, Assigned: Blake Ross)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 obsolete attachment)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Build Identifier: Firebird .6

here is the code:
<p><b><span class="TXTSubHead">Sections Covered in this Privacy Policy:<br>
								</span></b></p>
						<ul>
							<li><a 
href="#infocollect"><span class="TXTBody">Information Collection and 
Use</span></a>
							<li><a 
href="#cookies"><span class="TXTBody">Use of Cookies</span></a>
							<li><a 
href="#confidentiality"><span class="TXTBody">Confidentiality and 
Security</span></a>
							<li><a 
href="#updating"><span class="TXTBody">Updating User Preferences</span></a>
							<li><a 
href="#changes"><span class="TXTBody">Policy Changes</span></a>
						</ul>
						<p><a 
name="#infocollect"><b><span class="TXTSubHead">Information Collection and 
Use<br>
								
	</span></b></a><span class="TXTBody">We collect the following 
information:</span></p>
						<ul>
							<li><span 
class="TXTBody">email addresses of those who communicate with us via 
email</span>
							<li><span 
class="TXTBody">aggregate information on what pages consumers access or 
visit</span>
							<li><span 
class="TXTBody">information volunteered by the consumer, such as survey 
information and/or site registrations</span>
							<li><span 
class="TXTBody">personal information including address information given to us 
by the consumer when registering or making purchases on our site</span>
						</ul>
						<p><span class="TXTBody">The 
information we collect is used to improve the content of our Web pages, and is 
not shared with other organizations for commercial purposes. IPS collects 
personal information when you register on our website, when you purchase IPS 
products or services, and when you visit IPS pages. Once you register or place 
an order with IPS, you are not anonymous to us. IPS automatically receives and 
records information on our server logs from your browser, including your IP 
address, IPS cookie information, and the pages you request.</span></p>
						<p><span class="TXTBody">IPS 
uses information for the following general purposes:</span></p>
						<ul>
							<li><span 
class="TXTBody">to fulfill your requests for products and services</span>
							<li><span 
class="TXTBody">to customize the advertising and content you receive from 
IPS</span>
							<li><span 
class="TXTBody">to improve our services</span>
							<li><span 
class="TXTBody">to contact you</span>
							<li><span 
class="TXTBody">to conduct research</span>
							<li><span 
class="TXTBody">to provide anonymous reporting for internal and external 
clients</span>
						</ul>
						<p><span class="TXTBody">IPS 
does not rent, sell, or share personal information about you with other people 
or nonaffiliated companies except to provide products or services you've 
requested, when we have your permission, or under the following 
circumstances:</span></p>
						<ul>
							<li><span 
class="TXTBody">We provide the information to trusted partners who work on 
behalf of or with IPS under confidentiality agreements. These companies may use 
your personal information to help IPS communicate with you about offers from 
IPS and our marketing partners. However, these companies do not have any 
independent right to share this information.</span>
							<li><span 
class="TXTBody">We respond to subpoenas, court orders, or legal process, or to 
establish or exercise our legal rights or defend against legal claims.</span>
							<li><span 
class="TXTBody">We transfer information about you if IPS is acquired by or 
merged with another company. In this event, IPS will notify you before 
information about you is transferred and becomes subject to a different privacy 
policy.<br>
								</span>
						</ul>
						<a href="#top"><span 
class="TXTBody">Back to Top</span></a>
						<p><a name="#cookies"><b><span 
class="TXTSubHead">Use of Cookies<br>
								
	</span></b></a><span class="TXTBody">IPS may set and access IPS cookies 
on your computer. We use cookies to store consumer preferences, record session 
information such as items that you add to your shopping cart, and to record 
user-specific information on what pages you access or visit.<br>
							</span><a 
href="#top"><span class="TXTBody">Back to Top</span></a></p>
						<p><a 
name="#confidentiality"><b><span class="TXTSubHead">Confidentiality and 
Security<br>
								
	</span></b></a><span class="TXTBody">We limit access to personal 
information about you to employees who we believe reasonably need to come into 
contact with that information to provide products or services to you or in 
order to do their jobs.</span></p>
						<p><span class="TXTBody">We 
have physical, electronic, and procedural safeguards that comply with federal 
regulations to protect personal information about you. In certain areas, IPS 
uses industry-standard SSL-encryption to protect data transmissions.<br>
							</span><a 
href="#top"><span class="TXTBody">Back to Top</span></a></p>

Reproducible: Always

Steps to Reproduce:
1.See code provided....no steps to follow as its a general browser bug in link 
recognion
2.
3.

Actual Results:  
nothing....link didn't go to anchor

Expected Results:  
When you click on a link it should go to the anchor point on the page that was 
specified

Side note: In the Tools/Option window of Firebird when you click on the 
download manager history button you see the definition but also see a 
developers note to another programmer.

:)

Comment 1

15 years ago
*** Bug 213009 has been marked as a duplicate of this bug. ***
Is this a problem in a current Mozilla build?  If so, please attach a complete
testcase using
http://bugzilla.mozilla.org/attachment.cgi?bugid=213008&action=enter (not just a
tiny snippet).  If not, please move this to the firebird product.

Comment 3

15 years ago
The bug also happens under Linux Redhat 8 in a VNC Client in the latest
(to-date) Mozilla Firebird Nightly Build.  It only happens on one version of our
site (sorry, none of it is public); even though it is the exact same code base,
it only happens on one tree.

I have tried to delete my cache and closing the browser and checking to ensure
there are no other processes of it running with ps, but nothing effects the
issue.  The only work-around is too click a few times on the link and usually it
will work then (this does not fix the link ... you have to do this every time
you want to click on the link).  Also, the problem only sprouted up.  I did not
install the browser and then suddenly have this problem; rather the problem just
suddenly happened after a decent amount of use.

Comment 4

14 years ago
Is this still a problem with Firefox 0.8 or newer? Without a testcase this bug
isn't of much value.

Updated

14 years ago
Assignee: general → firefox
Component: Browser-General → General
Product: Browser → Firefox
Version: Trunk → unspecified

Comment 5

14 years ago
Created attachment 143965 [details]
Code copied from bug text

VARIFIED: Clicking links to anchors does not work.

Comment 6

14 years ago
Comment on attachment 143965 [details]
Code copied from bug text

Delete me...invaled
Attachment #143965 - Attachment is obsolete: true

Comment 7

14 years ago
Reporter, the problem is because you are using the # symbol in your anchor
names. Removing the # seems to correct the problem, please confirm.

Comment 8

14 years ago
It is not valid to have an anchor with a "#" in the name.  From
http://www.w3.org/TR/html4/intro/intro.html#fragment-uri, a description of a
fragment identifier:

"Some URIs refer to a location within a resource. This kind of URI ends with "#"
followed by an anchor identifier (called the fragment identifier). For instance,
here is a URI pointing to an anchor named section_2:

http://somesite.com/html/top.html#section_2"

And now, from the RFC (http://www.ietf.org/rfc/rfc2396.txt), information on
valid characters for use in a URI:

"2.4.3. Excluded US-ASCII Characters

   Although they are disallowed within the URI syntax, we include here a
   description of those US-ASCII characters that have been excluded and
   the reasons for their exclusion."

down a little further in the document:

"The character "#" is excluded
   because it is used to delimit a URI from a fragment identifier in URI
   references (Section 4)."


I will therefore close the bug report, and mark it as invalid.  

Out of interest, I tested this in IE, and IE does not follow the RFC, and allows
fragment identifiers to contain #'s.  This is a bug in IE, file a report with
Microsoft :)
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.