Issues which must be addressed prior to the next release (1.46?, 2.00?)

[smblott-github]

Chrome-store installs and sessions API

See discussion in #1166.

(Edit: We need to verify that adding a dependency on a recently-released chrome extension API (sessions) doesn't break chrome-store installations on older chrome versions.)

More edit:

• This is relevant.

[smblott-github]

Edit 2014/11/12: This is resolved in #1239 -- no favicons.

Favicons in vomnibar

Prior to the next release, we must do one of the following:

• Fix the CSP issue discussed in Better vomnibar favicons (fix for domains and security issues) #1210.
• Remove or disable favicons in the vomnibar (as currently in master).

[smblott-github]

The exclusion-rules section of the options page currently looks like this:

This style is a change from the established vimium option style, which is configuration by flat text area.

We need to either:

• Make a positive decision to go with this style.
• Revert to a flat text area.

[deiga]

This stile looks good to me, but does this allow for combinations to pass through? (f.ex. ctrl+d)

[smblott-github]

does this allow for combinations to pass through?

This is not (yet) implemented. It would be nice to have for the next release, but is not (in my view) a show stopper.

[mrmr1993]

I vote for text-based.

Since we still have time until release, I'd like to work on the idea in #1188 (any more feedback is much appreciated!), which should make passkeys largely redundant anyway.

[deiga]

@mrmr1993 after some consideration I do favor the way #1188 would change the whole thing

[philc]

Why don't we create separate issues for each of these, and give them a label of "release blocker" or "next-release"?

[smblott-github]

Closing. The most critical issue here is now its own issue: #1241.