-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only have one notifications option in RECAP, not two. #193
Comments
I am...actually not sure that's true. As a classic FF user, I traditionally had notifications on, and my OS default made them audible as well as an ephemeral notice window in a corner of my screen. In relatively recent months, I found myself doing more PACER work than in the past, and it got to the point where I disabled the audio (esp. because it would occur seemingly multiple times for the "login" notice). I was kind of looking forward to experimenting with the recap-chrome extension's more fine-grained options. I think I'd like a notice, maybe audible, with the upload, but not with "login," whatever that means. But I'm not sure. (And I haven't had a chance to experiment with that in the new extension since it took all my discretionary time to try to get baseline functionality working, cf. #182).
Seems like taking away features should not be on the priority list ahead of feature parity in the days before the public release that is time-sensitive driven by external deadlines. |
This code is already in place, I'm afraid, and about to land. On this one, I'm making an executive decision to simplify, especially since it's not a big difference to get a few more notifications when RECAP activates — plus, this brings us closer to old FF parity. It already feels nicer to me having fewer options. |
This fits in with #185, because it'll allow us to have a simpler dialog box. Right now it has two options:
People like notifications or they don't. Let's just have one notification box, eh? Once that's done, it'll be easier to add a choice for file names, and I think we'll be off to the races.
The text was updated successfully, but these errors were encountered: