Open GoogleCodeExporter opened 9 years ago
Original comment by odva...@gmail.com
on 19 Aug 2008 at 8:43
Original comment by odva...@gmail.com
on 22 Aug 2008 at 2:05
Do you have any tips how the UI could be designed for this?
Honza
Original comment by odva...@gmail.com
on 2 Sep 2008 at 6:07
I would say either under the filter tab an option, click on it, get a tiny
popup with
an input field a filter button and a + help sign.
Clicking on the + help sign wil increase the window size and display some tips
(like
* = wildcard)
Or, next to the firebug search bar in the right (or both ;) )
Original comment by Kja...@gmail.com
on 3 Sep 2008 at 7:49
I like the idea with the tiny popup panel.
Original comment by odva...@gmail.com
on 24 Sep 2008 at 11:55
A simple alternative that will cover 80% of the use cases would be to simply
group
the cookies by domain. This way, we can collapse the domains we aren't
interested in
and expand the domain we are interested in. I imagine this would be easier than
implementing full domain filters.
Also, a nice simple design for the domain/path filter panel as discussed above
would
be to copy the UI used by IETab's domain filtering.
Original comment by jason.ka...@gmail.com
on 2 Jun 2010 at 8:08
Issue 19 has been merged into this issue.
Original comment by sebastia...@gmail.com
on 15 Jun 2012 at 5:25
> A simple alternative that will cover 80% of the use cases would be to simply
group
> the cookies by domain.
That's what Dragonfly does and I think it's a good idea.
> I would say either under the filter tab an option, click on it, get a tiny
popup
> with an input field a filter button and a + help sign.
Instead I'd suggest to simply add a checkbox "Domain" to the search options
panel allowing to just filter by domain. See the related issue 3560.
Furthermore issue 4829 describes some very advanced filtering.
Note that Firecookie is integrated into Firebug since version 1.10a11.
Sebastian
Original comment by sebastia...@gmail.com
on 25 Jun 2012 at 12:28
Moved to: Issue fbug:5613
Original comment by sebastia...@gmail.com
on 25 Jun 2012 at 12:28
Original issue reported on code.google.com by
Kja...@gmail.com
on 28 Jul 2008 at 9:02