Technically if the text is inside a collapsed node it
doesn't exist on the page for firefox to walk and find.
There is nothing slash could do about it, if you want to do
a global page search you will have to expand everything, it
doesn't cost you any loading time to expand it so just do it.
I just tested it, and fully collapsed comments are indeed
excluded from the search which I feel is the correct behaviour.
If you are used to searching whole text anyway in the old
system, then you should set your threshholds to the old
levels so the same amount of text is found, remember in the
old system not all comments were even loaded so searching a
page wouldn't fina anything anyway.
Hang on, you say you search for words *you* type, I know
what the problem is here:
Old article system used to ALWAYS display comments made by
the logged in user even if the comment was under the
threshold (as long as the thread was visible), a -1 comment
made by me would display even if my threshold was 2 and above.
The new system treats comments made by the logged in user as
normal comments and folds them up if they are under the
threshold.
I think I mentioned this to Jamie a while back in an email
discussion.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is rather big - I wonder if that's the problem. The word
I was wanting to find is "shield" - The walk through using
F3 moves the pages each time but does not highlight the word.
I hope that helps
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I see this now in search mode.
I had to load the entire text and change my threshold to
display abbreviated comments (on the page it results in
85full,1032abbrev,0hidden).
Where a comment is displayed in abbreviated format firefox
will search ALL the comment text even if most of it is
offscreen.
When it finds a match, it puts the highlight onto it but
because its been clipped, you cannot see the cursor or
highlight but the page has been scrolled into position.
I therefore think this is a firefox thing, can anybody
confirm this behavious in other browsers?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for your help. So it's not really a bug. On your
suggestion I'd now prefer to use the HIDDEN mode so that at
least I can find the word in question and not get left
staring at something that doesn't make sense.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=883883
Wouldn't this come under a firefox thing?
Technically if the text is inside a collapsed node it
doesn't exist on the page for firefox to walk and find.
There is nothing slash could do about it, if you want to do
a global page search you will have to expand everything, it
doesn't cost you any loading time to expand it so just do it.
I just tested it, and fully collapsed comments are indeed
excluded from the search which I feel is the correct behaviour.
If you are used to searching whole text anyway in the old
system, then you should set your threshholds to the old
levels so the same amount of text is found, remember in the
old system not all comments were even loaded so searching a
page wouldn't fina anything anyway.
Hang on, you say you search for words *you* type, I know
what the problem is here:
Old article system used to ALWAYS display comments made by
the logged in user even if the comment was under the
threshold (as long as the thread was visible), a -1 comment
made by me would display even if my threshold was 2 and above.
The new system treats comments made by the logged in user as
normal comments and folds them up if they are under the
threshold.
I think I mentioned this to Jamie a while back in an email
discussion.
Logged In: YES
user_id=137198
here is the discussion topic in question
http://slashdot.org/article.pl?sid=06/08/21/173253&from=rss
It is rather big - I wonder if that's the problem. The word
I was wanting to find is "shield" - The walk through using
F3 moves the pages each time but does not highlight the word.
I hope that helps
Logged In: YES
user_id=883883
I see this now in search mode.
I had to load the entire text and change my threshold to
display abbreviated comments (on the page it results in
85full,1032abbrev,0hidden).
Where a comment is displayed in abbreviated format firefox
will search ALL the comment text even if most of it is
offscreen.
When it finds a match, it puts the highlight onto it but
because its been clipped, you cannot see the cursor or
highlight but the page has been scrolled into position.
I therefore think this is a firefox thing, can anybody
confirm this behavious in other browsers?
Logged In: YES
user_id=137198
Thanks for your help. So it's not really a bug. On your
suggestion I'd now prefer to use the HIDDEN mode so that at
least I can find the word in question and not get left
staring at something that doesn't make sense.