173606 - [type ahead] Korean : search stops at the end of page

Status: RESOLVED EXPIRED

(SeaMonkey :: Find In Page, defect)

Description

[Jeesun Cho]

[type ahead] Korean : search stops at the end of page
Build: 1004 trunk build on windows xp

Setup: Go to a Korean Site (e.g.: www.chosun.com )

Steps:
1. Turn on Korean IME
2. Type a word
3. Keep hitting F3 until you reach the bottom of the page
4. When you hit the last instance of the word you're searching, the search
should start over again from the top if you keep pushing F3 button. (That's what
happens with JA and EN char search)

Comment 1

[Jeesun Cho]

QA contact over to me.

Comment 2

[Jessie Li]

You should check "Wrap around" in "Find in this Page" dialog, opened by clicking
Ctrl+F.

Comment 3

[Aaron Leventhal]

I don't think the Find dialog's "wrap around" feature will reflect on type ahead
at all.

Kyle, do you have any ideas for this one?

Comment 4

[Kyle Yuan]

WFM on chinese site.

jessie might confuse the typeahead find with Edit/Find.

Comment 5

[firemotion+mozilla]

Same behaviour now with EN char search, since 1.4a
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030401

1. Find as you Type
2. F3 until end of page
3. Search stops at end of page

Also, scrolling up by keyboard (pgup/home) doesn't make any searches (ctrl+F or
Find as you Type) start from top.

Comment 6

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 7

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 8

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 9

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420