My favorites | Sign in
Project Home Wiki Issues
New issue   Search
  Advanced search   Search tips   Subscriptions
Issue 5036: default parameters facility
2 people starred this issue and may be notified of changes. Back to list
Reported by, Dec 8, 2011

How about a faciltiy to set parameters for every request...

If there were a tab or a frame in which a user could specify key=value pairs in sets that could be enabled and disabled as required.  The parameters would then be included with every request the browser makes (for each enabled set) regardless of whether they have been defined in the url or forms on the page.

Perhaps also the facility to specify whether the user-defined parameter sets should override those on the page (in forms or urls) where present.

Dec 8, 2011
This sounds fine to make it into an extension for Firebug.
Can you please describe more precisely how you imagine that?! will help you with that.


Status: NeedInfo
Labels: extension-request net Test-case-needed
Dec 9, 2011
I think the best place for it to go would be to have a separator and a "Parameters" button after the Media button in the "Net" tab.

In the view have a tabular list, one row per parameter, 3 columns.  Column 1 to contain a checkbox that specifies if the row is in use for the next page request, call it "Active" perhaps.  Column 2 to be the parameter name, column 3 to be the parameter value.

Then have 2 additional checkbox options at the top (or just somewhere convenient in view), one to specify whether the parameters override any that are submitted from the page, and the other to specify whether or not to include the parameters in the other supplementary requests on the page (for images, JS, etc).

So.. as the page submits the additional parameters in the extension get added into the request and if the override checkbox is selected then for the main page request replace any parameters in it with names that match with the values in the extension.

Dec 9, 2011
Now it's clearer, thanks.

Status: Triaged
Mar 23, 2013
Project Member #4
(No comment was entered for this change.)
Apr 4, 2013
Project Member #5
This could also go hand in hand with issue 2348. I.e. first you intercept the request, then you change the parameters. This issue would be about persisting the set parameters.

Labels: Type-Enhancement
Sign in to add a comment

Powered by Google Project Hosting