https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&format=guided should warn at the very beginning that its not a place for webpage rendering errors and especially step2 about the URL URL that demonstrates the problem you are seeing (optional.) IMPORTANT: If you are filing a bug about a broken web page, please read the Mozilla Web Developer FAQ, which explains how we handle old or badly-coded web pages. If somebody adds a URl here it should flag alarm signs, if it is a url issue than by 98% its not a ff issue

Actually, let me clarify. Here's the more specific problem. It seems that when a user doesn't select a product option, they get access to more privledges than they're allowed. A drop down, like this page, would help fix this. Matthew Newman NBC Universal

what do you think, Asa? I think we have that covered now with the "Report a broken website" link in the red box on the front page now (which didn't exist when this bug was filed).

Let me disagree that the reporter and the link does solve the problem. As Gerv may wittness there are tons of unconfirmed bugs wrongly filed that get never looked at. The key point of this bug is that https://bugzilla.mozilla.org/enter_bug.cgi does not show that core bugs dont belong into product categories. Just have a look at that page and assume that you have found a misbehaviour on a page that you have authored and you are using firefox. Which component would you choose, firefox of course and then comment 0 happily applies.

I think that the product selection screen could certainly have a link to the "Report a broken website" page, to try and divert people. That covers both bug-filing pathways - normal and guided. Gerv

Are we still seeing problems with web-page rendering issue bugs filed? Gerv

Just the last 10 bugs from /dev/null aka ff general: - Cookies expire after each session of Firefox 3.0 RC2 session is closed. - page partially loads, displays a large black window then returns to initial view. -Open two tabs > try to exit > cancel > close one tab > another tab will be shown blank - notify message is sliding too slow - DOM performance downgrade in FF3.x - Crash if dragging picture during javascript alert - SSL Certs cannot have an exception added on localhost - multiple unclosed center tags result in page rendering failing - On Print-preview and printouts, z-index isn't applied correctly - Unable to "escape" the infinite alert loop - In a scrolling table, the rows' background color continues to be drawn below the height of the overflow area. I would say the majority is core, while not exactly web page issues the majority of the bugs is filed in the wrong component

Bernd: I'm not sure there's any solution to the problem of people not knowing what component to file in. People don't have the patience to read 30 or 40 component descriptions, and unless we tell them we'd rather not have their bugs at all, I'm afraid we're just going to have to keep triaging out of FF General. Gerv

Gerv, this is not a problem about reading, but a problem with this page there is *NO* way to enter a core bug correctly with this form regardless how much you read. This a bug about a broken by design process which can not lead to correct results. If you tell me that you would know from the very beginning that at https://bugzilla.mozilla.org/enter_bug.cgi?&format=guided one has to select "Other products" to enter a layout bug than I am bowing before your genius. I do not understand why it is so difficult to add something like If you have reduced test case (link to bugathon ) for the broken web page rendering please consider entering a bug under https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&format=guided and make this appear once a URL is entered. This is in my opinion a solution to the problem that we give them at least a chance to file correctly, which we currently do not.

Bernd: My point is that anyone who knows that the bug they are submitting needs to go in the "Layout" component should not be using the Bugzilla Helper, because they should have canconfirm or editbugs privileges. (If there are people you think should have these privileges, let me know. That includes most people participating in the Bugathon.) And if they don't know it's supposed to go there, giving them an even larger list of options to choose from just increases the possibility that they'll misfile it somewhere random. Firefox General may be a collection of random stuff, but at least it's all in one place. Would we be in a better situation if, say, 20% of those bugs were filed in the correct component, but the other 80% were scattered across a load of different, incorrect components? At least having them filed in Firefox General means that they get found, and put in the right place. The Bugzilla Helper is already more complicated and scary than I'd like it to be. Asking people to choose from another set of options where they have very little understanding of the choice will not improve matters. Gerv

(In reply to comment #8) > If you tell me that you would know from the very beginning that at > https://bugzilla.mozilla.org/enter_bug.cgi?&format=guided one has to select > "Other products" to enter a layout bug than I am bowing before your genius. Yeah, I find this very strange too. I don't really read it anymore, but it is indeed, very confusing.