Open GoogleCodeExporter opened 9 years ago
I like the idea. Any tips how to UI should looks like? Perhaps cookie
breakpoints could be somehow utilized...?
Honza
Original comment by odva...@gmail.com
on 19 Oct 2010 at 9:16
Thanks Honza for the positive comments.
For the UI, I am thinking there can be another option under cookies section for
configuring rules for monitoring the cookies. It can take following
information:
Name:RuleOption:TimeStamp:IgnoreString:Status:
- Name: name of cookie or cookielet
- RuleOption: value [CHANGE|NOCHANGE] - option to tell how should the cookies behave
- TimeStamp: value [8|0] - 8 means cookie has timestamp and should be ignored; 0 means cookie does not have timestamp
- IgnoreString: value [BLANK|%3B|...] - BLANK means no string to ignore, %3B means string to be ignored within a cookie or cookielet's value
o Example:
o cookie_abc:NOCHANGE:8::
o cookie_2=:NOCHANGE:0::
Then some button (Cookie button) may turn red indicating that the rule has been triggered. On click of the button, it can show the errors and change in values.
Thanks.
Cheers,
Adee
Original comment by adee...@gmail.com
on 20 Oct 2010 at 1:57
It sounds like this issue is all about recognizing cookie changes.
So "Break On Cookie Change" covers the JavaScript changes and the rest should
be covered by checking the option "Show Logs in Console".
Adee, is that enough for you?
Please note that Firecookie is integrated into Firebug since version 1.10a11.
Sebastian
Original comment by sebastia...@gmail.com
on 25 Jun 2012 at 12:01
Moved to: Issue fbug:5611
Original comment by sebastia...@gmail.com
on 25 Jun 2012 at 12:01
Original issue reported on code.google.com by
adee...@gmail.com
on 12 Oct 2010 at 1:42