Asa Dotzler wrote:
Asa asked me to comment on this thread. Sorry, but I haven't been following npm.layout and am late to this. Overall, I have no problem with the classification scheme. It provides a limited means of grouping errors as well as a hint to the investigator what kinds of symptoms to look for in the site.
The only new suggestion I have is to consider that a person who uses this tool has a problem with our browser and we should try to help them if possible. We should provide links to pages which contain information about common causes of the types of problems and how to resolve them if possible. Think problems caused by cookie settings, popup blocking, ad blocking, dpi settings, etc.
Browser crashes Browser freeze
Do Ma and Pa Kettle really know what a crash or freeze is? Is there a non-techie way to say this? If we keep this, I suggest combining them as Safari does.
If these can't be used to submit information and are only to filter other reports into other categories, I would recommend just dropping them. However, it would useful to provide a page which described what happens during a crash, why installing talkback and submitting reports is good and a suggestion about filing a crash bug in bug if they are up to it.
Can't log in / Can't access page / Blocked *
Robert asked if a login problem is not related to our being blocked "is it really our problem?" Yes, since many log in problems have to do with cookie settings and/or cookie bugs. I think "Can't log in" should be a separate category from the other subcategories. How about "Browser not supported" instead of "Blocked"? That is usually the type of message sites give to us.
Again, providing information to the user about problems that cookie settings etc may cause might be helpful. If there is a user caused configuration problem, it would be best to at least try to tell them a few steps they can take themselves to resolve the issue rather than just leaving them borked.
Blank page Content missing
I agree with the others that these could probably be combined into just "Content Missing" although if Safari makes the distinction we might wish to follow their lead.
Behavior wrong Appearance wrong Plugin won't load Other problem
Anyway, I think this is a good idea that has been long in coming and I look forward to seeing the results.
/bc _______________________________________________ mozilla-layout mailing list [email protected] http://mail.mozilla.org/listinfo/mozilla-layout
