when in "view | By Site" or "view | By Date and Site" modes in the history sidebar, javascript: urls should not be displayed

RESOLVED WORKSFORME

Status

()

RESOLVED WORKSFORME
11 years ago
9 years ago

People

(Reporter: moco, Unassigned)

Tracking

2.0 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

when in "view | By Site" mode in the history sidebar, javascript: urls should not be displayed

steps to reproduce:

1)  in your url bar, type javascript:2+2
2)  in hour history sidebar, do view | by site

you'll see an item (not a folder) for "2+2".  perhaps we should not show javascript urls when in view by site mode.

same goes for date and site mode.

related note:  clicking on an unbookmarked javascript url in the history sidebar will give you a warning dialog (see http://lxr.mozilla.org/seamonkey/source/browser/components/places/content/utils.js#1259)
Depends on: 378632
Summary: when in "view | By Site" mode in the history sidebar, javascript: urls should not be displayed → when in "view | By Site" or "view | By Date and Site" modes in the history sidebar, javascript: urls should not be displayed

Comment 1

10 years ago
WFM
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090119 Minefield/3.2a1pre
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WORKSFORME
Bug 451915 - move Firefox/Places bugs to Firefox/Bookmarks and History. Remove all bugspam from this move by filtering for the string "places-to-b-and-h".

In Thunderbird 3.0b, you do that as follows:
Tools | Message Filters
Make sure the correct account is selected. Click "New"
Conditions: Body   contains   places-to-b-and-h
Change the action to "Delete Message".
Select "Manually Run" from the dropdown at the top.
Click OK.

Select the filter in the list, make sure "Inbox" is selected at the bottom, and click "Run Now". This should delete all the bugspam. You can then delete the filter.

Gerv
Component: Places → Bookmarks & History
QA Contact: places → bookmarks
You need to log in before you can comment on or make changes to this bug.