25Jan/10Off
Status update: Tab matches in Awesomebar, Extension Manager UI
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.
No related posts.
My blog, my words
Join Mozilla
Recent Posts
- The Add-ons Manager and I are rather good chums
- Solving Firefox’s add-on compatibility problem
- 7 Things About Me 2
- Mozilla in New Zealand
- Status Update: AppTabs, Extension Manager UI
Categories
- Firefox (36)
- House Redesign (1)
- Mozilla (49)
- New Zealand (1)
- Personal (6)
- Status Update (13)
- Taskfox (4)
- Ubiquity (9)
Twitter: theunfocused
- if no one hears from me in the next 5 days, i'm not dead - i'm just on holiday, without internet access. which is different from dead.
- @ChristianSonne like a boss
- almost 3am, and i have an early morning meeting. you'd think i'd learn...
- @brianking k, done
- @brianking compatible-by-default does apply to 3rd party addons. but they're opt-in, but that's separate from compatibility (added in Fx8)
- RT @standardistas: Unicode 6.1 has been released, finally including the essential (U+1F4A9) character: http://t.co/NKaK8ECm
- @IRCCloud i keep getting disconnected from http://t.co/VWCA5CJv :\ apparently due to Max SendQ exceeded
- @jmuenster nope, not this time
- @jmuenster no, still further/long that way (i checked)
- @EnglishMossop @dria @johnath i have no objections to going multiple times
January 25th, 2010 - 13:11
Isn’t “%” used in URLs already?
January 25th, 2010 - 13:26
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.)
January 25th, 2010 - 13:51
Oh I see, yeah. Not terribly discoverable, no, but very powerful.