Status update
15
Nov2
Nov2
Tab matches in Awesomebar
Status
- Took an alternative (more complete, less hacky) approach to autocomplete integration, which took a lot longer. This way should allow easy ranking for tab-only matches.
Loose ends
- None
Next steps
- Finish autocomplete work
- Unit tests
- Preferences UI
Target for next week
- Finish autocomplete
- Unit tests
Binding for untrusted text in security dialogs
Status
- Initial planning
- Identified potential issues with implementing in only JS
Loose ends
- None
Next steps
- More research – especially into unmatched surrogates in UTF-16
Target for next week
- A better understanding of surrogates
Miscellaneous
- 519486 resurrected itself in some (new) popular lightweight themes – looking at ways to further improve the solution.
Reflections
- A hack can save time now, cost time later, and still be worth it.
- Beautiful code is not always useful code.
Related posts:
2 Comments »
Leave a comment
Join Mozilla
3:00 PM on November 15th, 2009
I’m not a programmer, though I have a pet bug I would like to see fixed.. and dunno if there is any person or group of people that specialize in the awesome bar..
I have a beef with https://bugzilla.mozilla.org/show_bug.cgi?id=317056
Its old. and I am sorta lost as to why it hasn’t been fixed.
YAY FOR AWESOMEBAR!
10:50 PM on November 15th, 2009
Adam: I had a quick look at that bug – unfortunately I don’t think its going to be a quick and easy fix. But its on my radar now for when I have time to look into it more thoroughly.