Status update
25
Jan3
Jan3
Tab matches in Awesomebar
Status
- “$” or “!” as the restrict character? Got i18n input: smontagu suggested “%” as a more common character on non-US keyboards
- Discovered a (small) issue with having such a normalized DB schema
- Unit tests (why do these take SO much time?!)
- In process of final code review
Loose ends
- None
Next steps
- Address reviewer’s comments
- Get SR review for API changes
Target for next week
- Final reviews and (finally) landing
Extension Manager UI Redesign
Status
- Meetings, plannings, and discussions, oh my!
Loose ends
- None
Next steps
- Bring UI in line with newer mockups
- Handle installing and updating
Target for next week
- Extract mockups from Boriss’s brain
- Act on said mockups
- Handle updates
Miscellaneous
- Firefox 3.6 released. Boo-ya!
Reflections
- 5am start to a 13 hour day makes the next day really difficult.
Related posts:
3 Comments »
Leave a comment
Join Mozilla
1:11 PM on January 25th, 2010
Isn’t “%” used in URLs already?
1:26 PM on January 25th, 2010
Yes, but that doesn’t really matter. Restrict characters (such as * to restrict results to only bookmarks, + to only tagged bookmarks, etc) only work if they’re the first character in the URLbar input. So inputting “foo%20bar” will just do a normal awesomebar query. It’s not until you input something like “% foo” that it will restrict the results to only tab matches.
(And yes, I realize how horribly undiscoverable that is.)
1:51 PM on January 25th, 2010
Oh I see, yeah. Not terribly discoverable, no, but very powerful.