whitespace should be stripped out of search engine names

NEW
Unassigned

Status

()

Firefox
Search
P2
normal
Rank:
35
3 years ago
8 months ago

People

(Reporter: Cww, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [hijacking][fxsearch])

(Reporter)

Description

3 years ago
UITelemetry tracks how often you use various one-off search buttons. This is really useful but it trips me up when the search engine reported has newlines in it (and honestly, whitespace, too). It would be nice not to have to deal with it (and also generally trim whitespace from search engine names as a rule)

for example:

other-
    Gbase.com Guitar Search
  .oneoff
This is not a problem only for telemetry. The gbase.com engine also causes the tooltip on its one-off button to be larger than other one-off tooltips, and the 'Search <engine>' text from bug 1110767 (the gray bar in the middle of the panel, when hovering a one-off button) also shows excessive whitespace.

Fixing this could also help a tiny bit to reduce hijacking, as I think we have observed some hijackers working around our rule of "no engine with the same name as a default engine" by appending some whitespace to the engine name.
Priority: -- → P3
Summary: Strip newlines from Telemetry for one-off search, search engine → whitespace should be stripped out of search engine names
Whiteboard: [hijacking][fxsearch]

Updated

2 years ago
Rank: 35
(In reply to Florian Quèze [:florian] [:flo] from comment #1)

> Fixing this could also help a tiny bit to reduce hijacking, as I think we
> have observed some hijackers working around our rule of "no engine with the
> same name as a default engine" by appending some whitespace to the engine
> name.

Some also add random punctuation signs, eg '!' or '®'. We should also strip these before duplication checks.
OS: Mac OS X → All
Priority: P3 → P2
Hardware: x86 → All
Version: 35 Branch → Trunk
(In reply to Florian Quèze [:florian] [:flo] from comment #1)
> I think we have observed some hijackers working around our rule of
> "no engine with the same name as a default engine" by appending some whitespace
> to the engine name.

As I understand you have the data to back the "hijackers" claim?
(In reply to Stefan Plewako [:stef] from comment #3)
> (In reply to Florian Quèze [:florian] [:flo] from comment #1)
> > I think we have observed some hijackers working around our rule of
> > "no engine with the same name as a default engine" by appending some whitespace
> > to the engine name.
> 
> As I understand you have the data to back the "hijackers" claim?

I had such data at the time I wrote comment 1, yes.
OK, how did you recognize that it was different from legitimately working around that rule and other bugs or anything like details?
It's not possible to have thousand of users hand-editing a file and doing the exact same change to the name and submission URL, especially to add an affiliation code in the submission URL.
(In reply to Florian Quèze [:florian] [:flo] from comment #6)
> It's not possible to have thousand of users hand-editing a file and doing
> the exact same change to the name and submission URL, especially to add an
> affiliation code in the submission URL.

Oh, it is possible and only extremely unlikely and where this is coming from?

I do not get how 'I think we have observed some hijackers working around our rule of "no engine with the same name as a default engine" by appending some whitespace to the engine name.' becomes editing and becomes hijacking in all cases and not working around 10 year old Mozilla bugs.
Assignee: nobody → standard8
Assignee: standard8 → nobody
You need to log in before you can comment on or make changes to this bug.