Suggestion - have other page elements on the Image Manager

RESOLVED EXPIRED

Status

SeaMonkey
UI Design
--
enhancement
RESOLVED EXPIRED
18 years ago
8 years ago

People

(Reporter: Cesar Eduardo Barros, Assigned: jag (Peter Annema))

Tracking

({helpwanted})

Trunk
helpwanted

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
Currently everybody makes web bugs using a 1x1 image; however, web bugs can also
be done with everything that is fetched by the browser when opening a page:
style sheets and javascript files, for instance.

Both should be treated like images are (being possible to setup mozilla to ask
before loading them, load them from the same site only, or never load them).

Comment 1

18 years ago
I think this needs some clarification - this is a suggestion to have other
elements on the page act like images & cookies, such as javascript & stylesheets
being fetched from another site, so you can prevent these from loading and/or be
prompted before loading them.  Personally, I think this would wreak havoc with a
lot of things, especially if you apply this to CSS, because you pretty much have
to completely re-render the page if it loads, and THEN you enable CSS. Oh well,
I guess this is for one of the developers to decide.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Another way to make web bugs → Suggestion - have other page elements on the Image Manager

Comment 2

18 years ago
Personally, I like this idea. Have a content panel in the prefs and give 
users the option to choose what content they want to be able to see and 
use. Am I on the right track here? Reassign to prefs for their feedback.
Assignee: asa → matt
Component: Browser-General → Preferences
QA Contact: doronr → sairuh
over to morse, who owns Image management (and cookie management).
Assignee: matt → morse
Component: Preferences → XP Apps

Updated

18 years ago
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Keywords: helpwanted
(Reporter)

Comment 4

18 years ago
(checking my old still open bugs...)

A comment above says it would cause redrawing if CSS is included in the list.
But you can just block drawing the page until the user answers the dialog (I've
already seen worse things in Mozilla; confirmations blocking all the other
windows' inputs, for instance).

Updated

17 years ago
Summary: Suggestion - have other page elements on the Image Manager → [z]Suggestion - have other page elements on the Image Manager

Updated

17 years ago
Summary: [z]Suggestion - have other page elements on the Image Manager → Suggestion - have other page elements on the Image Manager
Whiteboard: [z]

Comment 5

17 years ago
nav triage team:

Neat feature, but won't get to it for beta1, marking nsbeta1-
Keywords: nsbeta1-

Comment 6

17 years ago
.
Assignee: morse → nobody
Status: ASSIGNED → NEW
Whiteboard: [z]
Product: Core → Mozilla Application Suite
Assignee: nobody → jag
Priority: P3 → --
QA Contact: bugzilla
Target Milestone: Future → ---

Comment 7

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 8

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 9

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 10

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 11

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 12

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.