Bugzilla

The user should be able to Create, Read, Update and delete request/resource blocking patterns. These actions should be available within the `Request Blocking` side panel.

The UI will be similar to what we already have in Debugger for XHR Breakpoints.

See the attached mockup:

1) There should be a toolbar with two items:
  - Enable request blocking checkbox - is used to enable/disable all existing blocking patterns
  - Add new pattern button - located at the right side. Clicking the button opens new inline editor that can be used to add new pattern (plain text). Typing text in this editor and pressing the Enter key creates new pattern. Pressing Enter in empty inline editor just closes the editor.

2) There should be a list of existing patterns. Every item in the list should have:
  - a checkbox used to disable/enable the pattern
  - a text representing the pattern
  - a button used to delete the pattern

Double clicking the pattern opens an inline editor that can be used to edit the pattern.

The list of patterns is stored in a new reducer only ('RequestBlockingReducer'). It isn't persistent across Firefox sessions.

Honza

The user should be able to Create, Read, Update and delete request/resource blocking patterns. These actions should be available within the `Request Blocking` side panel.

The UI will be similar to what we already have in Debugger for XHR Breakpoints.

See the attached mockup:

1) There should be a toolbar with two items:
  - Enable request blocking checkbox - is used to enable/disable all existing blocking patterns
  - Add new pattern button - located at the right side. Clicking the button opens new inline editor that can be used to add new pattern (plain text). Typing text in this editor and pressing the Enter key creates new pattern. Pressing Enter in empty inline editor just closes the editor.

2) There should be a list of existing patterns. Every item in the list should have:
  - a checkbox used to disable/enable the pattern
  - a text representing the pattern
  - a button used to delete the pattern

Double clicking the pattern opens an inline editor that can be used to edit the pattern.

The list of patterns is stored in a new reducer only (`RequestBlockingReducer`). It isn't persistent across Firefox sessions.

Honza

The user should be able to Create, Read, Update and delete request/resource blocking patterns. These actions should be available within the `Request Blocking` side panel.

The UI will be similar to what we already have in Debugger for XHR Breakpoints.

See the attached mockup:

1) There should be a toolbar with the following items:
  - Enable request blocking checkbox - is used to enable/disable all existing blocking patterns
  - Add new pattern button - located at the right side. Clicking the button opens new inline editor that can be used to add new pattern (plain text). Typing text in this editor and pressing the Enter key creates new pattern. Pressing Enter in empty inline editor just closes the editor.
 - Remove all patterns button - located at the right side. Removes all patterns in the list (not at the screenshot)

2) There should be a list of existing patterns. Every item in the list should have:
  - a checkbox used to disable/enable the pattern
  - a text representing the pattern
  - a button used to delete the pattern

Double clicking the pattern opens an inline editor that can be used to edit the pattern.

The list of patterns is stored in a new reducer only (`RequestBlockingReducer`). It isn't persistent across Firefox sessions.

Honza