Watchlist problem

[Octopuss]

Whenever I open the watchlist and click on the small blue "new" icon in the name of a thread, it takes me to top of the last page instead of first unread post. Is this some known bug, or what's the deal here? Any ideas? I am using Firefox v26.

Also, why are unread posts not marked by some icon inside a thread? That would make the forum much more readable/less chaotic.

[whiskers75]

Get the Bitcointalk++ script, by jackjack (look in Meta).

[dudel42]

same problem here in Firefox -- the new # anchors stopped working one or two days ago for me.

[justusranvier]

Most likely it was one of the features that was consuming too much in the way of database resources so Theymos had to turn it off.

[Bagatell]

Most likely it was one of the features that was consuming too much in the way of database resources so Theymos had to turn it off.

A links a link, I can't see how it would use db storage.

[justusranvier]

A links a link, I can't see how it would use db storage.

Finding the most recently read post in a thread is a calculation that has to be performed on a per-user basis.

Although that might not be it, because it looks like all anchor links are broken.

[Bagatell]

A links a link, I can't see how it would use db storage.

Finding the most recently read post in a thread is a calculation that has to be performed on a per-user basis.

Remove the link from the watchlist then?

[theymos]

Nothing changed on the forum's end. This is probably a Firefox bug unless there's something invalid about the forum's XHTML.

[theymos]

I refuse to use shit browser

Why are you using Firefox, then?

I think that Firefox 26 is broken somehow. I'll investigate it when I can.

[jackjack]

I refuse to use shit browser

Why are you using Firefox, then?

I think that Firefox 26 is broken somehow. I'll investigate it when I can.

http://stackoverflow.com/questions/484719/html-anchors-with-name-or-id

According to the HTML 5 specification, 5.9.8 Navigating to a fragment identifier:

   For HTML documents (and the text/html MIME type), the following processing model must be followed to determine what the indicated part of the document is.

        Parse the URL, and let fragid be the <fragment> component of the URL.
        If fragid is the empty string, then the indicated part of the document is the top of the document.
        If there is an element in the DOM that has an ID exactly equal to fragid, then the first such element in tree order is the indicated part of the document; stop the algorithm here.
        If there is an a element in the DOM that has a name attribute whose value is exactly equal to fragid, then the first such element in tree order is the indicated part of the document; stop the algorithm here.
        Otherwise, there is no indicated part of the document.

So, it will look for id="foo" followed by name="foo"

Edit: As pointed out by @hsivonen, in HTML5 the a element has no name attribute. However, the above rules still apply to other named elements.

Could this be the reason?

See http://www.w3schools.com/tags/att_a_name.asp also


Edit: the forum uses

<a name="new"></a>

[MiningBuddy]

I refuse to use shit browser

Why are you using Firefox, then?

I think that Firefox 26 is broken somehow. I'll investigate it when I can.

I'm using FF 26 and everything is working as it should.
What browser do you use theymos?

[justusranvier]

Could this be the reason?

See http://www.w3schools.com/tags/att_a_name.asp also


Edit: the forum uses

<a name="new"></a>

The forum isn't HTML 5 though - it's XHTML 1.0 Transitional.

Firefox 26 here and I'm also seeing a complete failure of anchor links to resolve.

[dudel42]

the thing is, i haven't changed anything in my browser or OS setup in the last few days... and suddenly it stopped working in FF26. browser was not upgraded in the last days, so I can't believe nothing changed in the forum that broke it..?

[theymos]

It's a bug in EasyList for Adblock Plus. All links (including "anchor" links) are blocked when immediately inside of a post <td>:

Code:

bitcointalk.org##td[style="padding: 1px 1px 0 1px;"] > a

Complain to EasyList.

It's impossible for an Adblock Plus filter to block all of the forum's ads. Some ads can be individually blocked, but not all forum ads in general. They should stop trying or they're going to keep breaking things for their users.

[jackjack]

Don't they know the purpose of testing? 

[theymos]

What browser do you use theymos?

All browsers suck. I actually use Firefox (mostly) because it sucks a little less AFAICT, but I'm frustrated with it daily.

[TheButterZone]

This bugged me too. Disabled ABP on bitcointalk.org. Problem solved.

[TiagoTiago]

This bugged me too. Disabled ABP on bitcointalk.org. Problem solved.

I just disabled that rule in specific, and it seems to have worked

[dudel42]

It's a bug in EasyList for Adblock Plus. All links (including "anchor" links) are blocked when immediately inside of a post <td>:

Code:

bitcointalk.org##td[style="padding: 1px 1px 0 1px;"] > a

Complain to EasyList.

It's impossible for an Adblock Plus filter to block all of the forum's ads. Some ads can be individually blocked, but not all forum ads in general. They should stop trying or they're going to keep breaking things for their users.

thanks for figuring this out!