buggy queue

Beetles

Comments

Mark de LA says
End of scroll page looks like intent to have a next page - is that intensional ?

Mark de LA says
On most of my browsers the logout preserves the author and password fields (*****) - I think these should be cleared on logout.

Mark de LA says
The above is somewhat dangerous (or insecure) in internet cafes

Seth says

End of scroll page looks like intent to have a next page - is that intensional ?

No, had not thought of that, but i can see that interpertation of the graphics.

Mark de LA says
hmmmm... i would agree

Seth says

On most of my browsers the logout preserves the author and password fields (*****) - I think these should be cleared on logout.

I disagree. Though there should be a warning in the faq to logout if you are posting from an Internet cafe type environment. The wole rational of fastblogit is so that you do not need to go through extra protocols; consequently security is lax. This is intentional.

Seth says
I'm gonna declare it a bug that i cannot delete comments that i myself authored when they appear are against a item in another group

unknown says
do you want to distinguish between a bug and a peg ?

unknown says
IMHO i would rather that a link resolve to the URL instead of the word link if it is unlabeled. Here is a test - ]

unknown says
is a better test

faq says
I would say it is still useful to tag an item with "bug" which indicates that a bug was discussed somewhere in that item. A peg is a bit more formal. One item, one peg and only that peg should be discussed on that item. Also it is, if we use it that way, a controled list of current pegs. So that is the distinction between the tagroom bug and the title room peg

unknown says
apparently bracketing 2 urls separated by a space doesn't work

unknown says
http://fastblogit.com/Test%20and%20QA/item/422/>

unknown says
link is another test

anonymous says
good old HTML does still work for now

Seth says
link link

Seth says
seemed to work for me ... try a different one one two

Seth says

apparently bracketing 2 urls separated by a space doesn't work
cannot reproduce

unknown says
try bracket URL1 URL1 endbracket

unknown says
doesnt work for me

unknown says
it just flushes the link entirely

Seth says

Seth says
ahh so it does, peg it

Seth says
the peg is here

Mark de LA says
** FINAL DETERMINATION ** 2 additional bugs here (besides the peg)

Mark de LA says
link

buggy queue

Tags

Comments

See Also