Bugzilla

There are a couple things that are apparently not tracked elsewhere, thus I'm annotating them here. They are potentially feasible in shippable increments and parallelizable, thus feel free to file as follow-ups if you think it's too much to do here.

1. the Remove from Address Bar option and the following HR should be removed from the context menu of actions in Proton.
2. we are discussing overflow in the Jira Spike, it may be worth supporting some kind of simple overflow behavior, and there I suggested to just hide/show all the actions depending on the window size, as a first step. So basically, if the window is smaller than a threshold, hide all the actions and unhide the meatball menu. This should be easy to do with simple CSS.

There are a couple things that are apparently not tracked elsewhere, thus I'm annotating them here. They are potentially feasible in shippable increments and parallelizable, thus feel free to file as follow-ups if you think it's too much to do here.

1. the Remove from Address Bar option and the following HR should be removed from the context menu of actions in Proton.
2. we are discussing overflow in the Jira Spike, it may be worth supporting some kind of simple overflow behavior, and there I suggested to just hide/show all the actions depending on the window size, as a first step. So basically, if the window (or the urlbar) is smaller than a threshold, hide all the actions and unhide the meatball menu. This should be easy to do with simple CSS.

There are a couple things that are apparently not tracked elsewhere, thus I'm annotating them here. They are potentially feasible in shippable increments and parallelizable, thus feel free to file as follow-ups if you think it's too much to do here.

1. the Remove from Address Bar option and the following HR should be removed from the context menu of actions in Proton. Or better, built-in actions should not have a context menu anymore, while extensions should only have Manage Extensions and Remove Extension.
2. we are discussing overflow in the Jira Spike, it may be worth supporting some kind of simple overflow behavior, and there I suggested to just hide/show all the actions depending on the window size, as a first step. So basically, if the window (or the urlbar) is smaller than a threshold, hide all the actions and unhide the meatball menu. This should be easy to do with simple CSS.

There are a couple things that are apparently not tracked elsewhere, thus I'm annotating them here. They are potentially feasible in shippable increments and parallelizable, thus feel free to file as follow-ups if you think it's too much to do here.

1. the Remove from Address Bar option and the following HR should be removed from the context menu of actions in Proton. Or better, built-in actions should not have a context menu anymore, while extensions should only have Manage Extension and Remove Extension.
2. we are discussing overflow in the Jira Spike, it may be worth supporting some kind of simple overflow behavior, and there I suggested to just hide/show all the actions depending on the window size, as a first step. So basically, if the window (or the urlbar) is smaller than a threshold, hide all the actions and unhide the meatball menu. This should be easy to do with simple CSS.

There are a couple things that are apparently not tracked elsewhere, thus I'm annotating them here. They are potentially feasible in shippable increments and parallelizable, thus feel free to file as follow-ups if you think it's too much to do here.

1. the Remove from Address Bar option and the following HR should be removed from the context menu of actions in Proton. Or better, built-in actions should not have a context menu anymore, while extensions should only have Manage Extension and Remove Extension.
2. we are discussing overflow in the Jira Spike, it may be worth supporting some kind of simple overflow behavior, and there I suggested to just hide/show all the actions depending on the window size, as a first step. So basically, if the window (or the urlbar) is smaller than a threshold, hide all the actions and unhide the meatball menu. This should be easy to do with simple CSS. We can keep doing something similar to comment 2.

There are a few things that are apparently not tracked elsewhere, thus I'm annotating them here. They are potentially feasible in shippable increments and parallelizable, thus feel free to file as follow-ups if you think it's too much to do here.

1. the Remove from Address Bar option and the following HR should be removed from the context menu of actions in Proton. Or better, built-in actions should not have a context menu anymore, while extensions should only have Manage Extension and Remove Extension. The same if we implement overflow for actions shown in the menu.
2. we are discussing overflow in the Jira Spike, it may be worth supporting some kind of simple overflow behavior, and there I suggested to just hide/show all the actions depending on the window size, as a first step. So basically, if the window (or the urlbar) is smaller than a threshold, hide all the actions and unhide the meatball menu. This should be easy to do with simple CSS. We can keep doing something similar to comment 2.

There are a few things that are apparently not tracked elsewhere, thus I'm annotating them here. They are potentially feasible in shippable increments and parallelizable, thus feel free to file as follow-ups if you think it's too much to do here.

1. the Remove from Address Bar option and the following HR should be removed from the context menu of actions in Proton. Or better, built-in actions should not have a context menu anymore, while extensions should only have Manage Extension and Remove Extension. The same if we implement overflow (see point 2), for actions shown in the menu.
2. we are discussing overflow in the Jira Spike, it may be worth supporting some kind of simple overflow behavior, and there I suggested to just hide/show all the actions depending on the window size, as a first step. So basically, if the window (or the urlbar) is smaller than a threshold, hide all the actions and unhide the meatball menu. This should be easy to do with simple CSS. We can keep doing something similar to comment 2.