43266 - Rethink dialog usage

Status: VERIFIED DUPLICATE of bug 28586

(Core :: DOM: Navigation, defect, P3)

Description

[Jeremy M. Dolan]

Is there currently any spec out for when dialogs should be displayed? It seems
very differant from 4.7 behaviour.

Viewing a frameset, if one of the frame's doesn't exsist, 4.7 pops up a dialog
saying so. M16 does nothing to indicate an error occured.

If an inline image isn't available to load, 4.7 does nothing, but mozilla will
pop up a dialog. This is very annoying, especially since I have a fake DNS entry
for doubleclick.net. This isn't serious enough of an error for such a server
notification. Should simply be showing a broken image icon.

Comment 1

[Doron Rosenberg (IBM)]

reporter, please file seperate bugs for each issue and mark em to the
corresponding component.

Comment 2

[Jeremy M. Dolan]

Reopening as a placeholder, will RFC n.p.m.ui, unless mpt wants to proceed here.

Comment 3

[Jeremy M. Dolan]

assigning default Owner/QA.

Comment 4

[Blake Ross]

this isn't ui, it's networking

Comment 5

[Brendan Donohoe]

Sorry, I don't understand how visible representation of error messages is 

a networking issue.  Can you clarify?

Comment 6

[Jeremy M. Dolan]

It's definatly UI. I'm asking for the currect design, the two examples may have 
been networking, but not all dialogs are. But whatever, I'll leave it and let 
the NSCP folks toss it back and forth.

Comment 7

[Blake Ross]

In each of the examples you provided, it would be networking that decides 
whether to throw up the dialog or not.  i.e. networking would determine whether 
an image is available to load, and then it would determine whether to throw out 
an error message or not.

UI would only come into play here, IMHO, in deciding such things as the 
appearance of the dialogs in question.  It would have to be the networking 
people who decide in what situations to spit out an error message...

(reassign back to UI if you disagree)

Comment 8

[Blake Ross]

okay, i'm wrong :) sorry

Comment 9

[Matthew T (active 1999-2002)]

This is scheduled to be fixed in M17.


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

Comment 10

[Blake Ross]

verified...the fix for that should cover most (if not all) of the cases 
mentioned here, we'll reopen this later if it doesn't


[mmm..odd how that bug is reported against networking..]

Comment 11

[Darin Fisher]

*** Bug 45131 has been marked as a duplicate of this bug. ***

Comment 12

[Jesse Ruderman]

*** Bug 69921 has been marked as a duplicate of this bug. ***

Comment 13

[Jesse Ruderman]

*** Bug 70084 has been marked as a duplicate of this bug. ***

Comment 14

[Matthias Versen [:Matti]]

*** Bug 131069 has been marked as a duplicate of this bug. ***