Closed Bug 167786 Opened 22 years ago Closed 22 years ago

typeahead messes up bitfluxeditor

Categories

(SeaMonkey :: Find In Page, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: timeless, Assigned: aaronlev)

References

()

Details

2002091008w32, typeahead enabled, caret browsing enabled

i didn't intentionally enable typeahead, i'm just using it to file other bugs
and andreww mentioned this cool demo. it worked at first.

then i clicked insert symbol and inserted some hebrew letters (arbitrary
choice), when i switched back to the demo clicked the bulleted list item and
started typing, everything went to typeahead instead of the document.

note that we had a similar bug in mailnews composer.
Depends on: 167921
Now I know, what you are talking about... Just downloaded the latest nightly
build and yes, our editor doesn't work anymore with typeahead :( (although
typeahead seems to be a cool feature normally..)

And e.preventDefault(); and e.stopPropagation(); in the keypress-event seems not
of much use to prevent that. 

But anyway, keep up the good work on mozilla, it's a pleasure to work with it :)

chregu
preventDefault() doesn't work yet, but I'm working to fix that in bug 167921.
Solution should come in the next week.
The fix for bug 167921 just got checked in - can you see if preventDefault fixes
the bitflux problem now?
Marking this fixed, since all the work on our done is finished.

The bitflux folks can either verify it or reopen it, if they have problems using
the preventDefault fix.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Component: Accessibility APIs → Keyboard Navigation
QA Contact: dsirnapalli → chregu
Just downloaded the latest nightly and Bitflux Editor seems to work again.
Thanks for the quick response :)

chregu
Component: Keyboard: Navigation → Keyboard: Find as you Type
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.