Closed Bug 346851 Opened 19 years ago Closed 19 years ago

LOAD_FLAGS_NEW_WINDOW naming doesn't make much sense

Categories

(Core Graveyard :: Embedding: APIs, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bzbarsky, Assigned: marria)

References

Details

(Keywords: fixed1.8.1)

Attachments

(1 file, 1 obsolete file)

For starters, "what's a window"? It's not a concept that's really attached well to nsIWebNavigation, at least as the interface stands. Wouldn't it make more sense to name the flag something like LOAD_FLAGS_FIRST_LOAD and document that this is the first "real" load being performed in this webnavigation (whatever that means)? That prevents misunderstandings like "well, it's the first load in the tab, but not the first one for the whole window". The comments should also mention what happens if this flag is set on a non-first load, in my opinion... Similar naming issue for the docshell internal load flag.
Requesting blocking, since once we ship this in Gecko 1.8.1 we won't be able to change it anymore...
Blocks: 241972
Flags: blocking1.9a1?
Flags: blocking1.8.1?
Decide ASAP, please :)
Flags: blocking1.8.1? → blocking1.8.1+
Attachment #232338 - Flags: review?(bzbarsky)
Attachment #232339 - Flags: review?(bzbarsky)
Comment on attachment 232338 [details] [diff] [review] change variable name and update comment whoops this posted twice for some reason
Attachment #232338 - Attachment is obsolete: true
Attachment #232338 - Flags: review?(bzbarsky)
Comment on attachment 232339 [details] [diff] [review] change variable name and update comment this makes one kind of wonder why the caller needs to keep track of whether this is the first load. but this naming does seem better.
Attachment #232339 - Flags: review+
Comment on attachment 232339 [details] [diff] [review] change variable name and update comment > why the caller needs to keep track of whether this is the first > load Hence my comments about "real" in comment 0. We want to exclude the default about:blank load, for example. >+ // This flag marks the first load in this object >+ const long INTERNAL_LOAD_FLAGS_FIRST_LOAD = 0x8; Add @see nsIWebNavigation::LOAD_FLAGS_FIRST_LOAD. I really wish I could figure out how to improve the nsIWebNavigation docs here, but nothing is coming to mind. :( sr=bzbarsky. Please land on the 1.8 branch too. Thanks!
Attachment #232339 - Flags: review?(bzbarsky) → superreview+
Comment on attachment 232339 [details] [diff] [review] change variable name and update comment checked in on trunk
Attachment #232339 - Flags: approval1.8.1?
Comment on attachment 232339 [details] [diff] [review] change variable name and update comment a=dbaron on behalf of drivers. Please land on MOZILLA_1_8_BRANCH and add the fixed1.8.1 keyword once you have done so.
Attachment #232339 - Flags: approval1.8.1? → approval1.8.1+
Assignee: nobody → marria
checked in on branch.
Status: NEW → RESOLVED
Closed: 19 years ago
Keywords: fixed1.8.1
Resolution: --- → FIXED
Flags: blocking1.9a1?
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: