328519 - I can't figure out this system. I want it fixed. It's bug number 314781

Status: VERIFIED DUPLICATE of bug 314781

(Firefox :: General, defect)

Description

[Mary Erickson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

when I go to pogo.com i can play only some of the games because some of the games 
require another popup window that wont open.  I do not get a bar that lets me allow the next popup.  when I disable the popup blocking it still does the same thing.  It wont let the windows open for certain games.  It also wont open the profile windows in the game rooms that I can get into etc..

Reproducible: Always

Steps to Reproduce:
1.I go to pogo and go to game room
2.some games work some games dont
3.profiles and some game rooms wont open




all popups associated with pogo.com should open to begin with, or, the bar should appear that lets you allow the popup.  and when the popup blocker is disabled, there should be nothing blocking the popups on the site!!  What is it?

Comment 1

[Philip Puryear]

Please don't give bugs aliases unless you're a Mozilla developer.

Also, by "It's bug number 314781," do you mean that this is the same issue as bug 314781? If not, what do you mean?

Comment 2

[Mary Erickson]

theres no way I could fill this form out ever.  Only a technician could understand this form.   Read below.  All of it.


[e-mail] changed:
 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
              Alias|pupblockernitemare          |
 
 
 
 
------- Comment #1 from [e-mail]  2006-02-24 13:59 PST -------
Please don't give bugs aliases unless you're a Mozilla developer.
 
Also, by "It's bug number 314781," do you mean that this is the same issue as
bug 314781? If not, what do you mean?




first of all, your system doesn't explain whether Im supposed to fill in the empty fields or not. And I see you have no sense of humor.  You need a more user friendly system that tells a person what they are supposed to do.  It didn't say this field is to be filled out by the Mozilla developers only.  and Many people have found the frustrations of being given forms that require fields filled in to submit them.  I didn't know if I had to put something in there or not, or where I was supposed to look up the information to fill that in.  There are no proper instructions.  Secondly yes it is aparently the same issue as bug 314781 from what I could tell by the limited amount of information it gave when I typed in my problem and it gave that information, then there was no link or instructions telling me where or how to let you know that my bug resembles the description for that one.  Your system is the problem, not my giving a bug an alias as a joke. I'm sure you knew it was a joke and that I had no clue what to put there, or that I wasn't supposed to put anything there.  YOUR company gave me that form to submit.  So I did my best. And I don't need the condescending retort of "Please don't give bugs aliases unless your a Mozilla deverloper" when there was no information about what to put or not put in that field. I know I'm not a Mozilla developer, and if I was, I'd be telling my company what's wrong with their system, instead of critizing confused clients of their product.  I just want it fixed and it's ridiculous to make people with no computer educations have to go link after link looking for answers that are almost impossible to find and then have to figure out what to do with your forms that don't have proper instructions.  all anyone should have to do is tell you what their Mozilla product is or isn't doing and then leave it in your hands to distribute the problem to the right department.  There are some people in the world who would have great difficulty with your system and reading all those bug report entries that don't even fully describe the problem.  sorting through those reports is a TECHNICIANS job.  They are written in a way only technicians can understand to begin with.  A trained technician for your company should be reading peoples complaints and looking up which bug it is and which number to assign to it and sending it on to the right department. I am not a technician, and didn't get your system.  And how can it be so unclear what I meant by "It's bug number 314781." It's a clear and concise statement.  And if it's a different problem than that, remember, that I have no clue over here what caused it and there is only a short sentence in the logs on your site that described the bug. Mine is like that one.  but I don't know the cause. I'm not the technician that would know.  You are. Tell your company to fix their system. And these bugs.  It's hackers that make these problems. And most people aren't trained tecnicians that can spell it out for you what the problem is.

[e-mail] changed:
 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
              Alias|pupblockernitemare          |
 
 
 
 
------- Comment #1 from [e-mail]  2006-02-24 13:59 PST -------
Please don't give bugs aliases unless you're a Mozilla developer.
 
Also, by "It's bug number 314781," do you mean that this is the same issue as
bug 314781? If not, what do you mean?

Comment 3

[Mary Erickson]

[e-mail] changed:
 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
              Alias|pupblockernitemare          |
 
 
 
 
------- Comment #1 from [e-mail]  2006-02-24 13:59 PST -------
Please don't give bugs aliases unless you're a Mozilla developer.
 
Also, by "It's bug number 314781," do you mean that this is the same issue as
bug 314781? If not, what do you mean?


first of all, your system doesn't explain whether Im supposed to fill in the empty fields or not. And I see you have no sense of humor.  You need a more user friendly system that tells a person what they are supposed to do.  It didn't say this field is to be filled out by the Mozilla developers only.  and Many people have found the frustrations of being given forms that require fields filled in to submit them.  I didn't know if I had to put something in there or not, or where I was supposed to look up the information to fill that in.  There are no proper instructions.  Secondly yes it is aparently the same issue as bug 314781 from what I could tell by the limited amount of information it gave when I typed in my problem and it gave that information, then there was no link or instructions telling me where or how to let you know that my bug resembles the description for that one.  Your system is the problem, not my giving a bug an alias as a joke. I'm sure you knew it was a joke and that I had no clue what to put there, or that I wasn't supposed to put anything there.  YOUR company gave me that form to submit.  So I did my best. And I don't need the condescending retort of "Please don't give bugs aliases unless your a Mozilla deverloper" when there was no information about what to put or not put in that field. I know I'm not a Mozilla developer, and if I was, I'd be telling my company what's wrong with their system, instead of critizing confused clients of their product.  I just want it fixed and it's ridiculous to make people with no computer educations have to go link after link looking for answers that are almost impossible to find and then have to figure out what to do with your forms that don't have proper instructions.  all anyone should have to do is tell you what their Mozilla product is or isn't doing and then leave it in your hands to distribute the problem to the right department.  There are some people in the world who would have great difficulty with your system and reading all those bug report entries that don't even fully describe the problem.  sorting through those reports is a TECHNICIANS job.  They are written in a way only technicians can understand to begin with.  A trained technician for your company should be reading peoples complaints and looking up which bug it is and which number to assign to it and sending it on to the right department. I am not a technician, and didn't get your system.  And how can it be so unclear what I meant by "It's bug number 314781." It's a clear and concise statement.  And if it's a different problem than that, remember, that I have no clue over here what caused it and there is only a short sentence in the logs on your site that described the bug. Mine is like that one.  but I don't know the cause. I'm not the technician that would know.  You are. Tell your company to fix their system. And these bugs.  It's hackers that make these problems. And most people aren't trained tecnicians that can spell it out for you what the problem is.

Comment 4

[Philip Puryear]

I'm sorry if my first comment seemed a tad harsh. It's just that there are certain fields in a bug report that only a developer is given authority to modify, and it's a little annoying when a reporter fills them in unawares, even if it was intended to be humerous (triagers have no sense of humor ;) ). As a rule of thumb, you should only fill in the fields that are in the bug-reporting page (http://bugzilla.mozilla.org/enter_bug.cgi?format=guided), not on the actual bug report itself, unless you're a triager or someone else associated with Mozilla.

The reason I was confused by your saying "It's bug number 314781" is that the usual process for filing a bug involves searching to see if that bug has already been reported, and if so, not filing a new one. It was a little off-putting to see a report that had been willingly filed in explicit knowledge that the problem had already been reported (as bug 314781), and that's why I asked you what you meant by your statement.

Thus, if this report does indeed describe the same issue as bug 314781, then these are duplicate bugs. So, as future reference, if the report already exists, there's no need to file a new one.

*** This bug has been marked as a duplicate of 314781 ***