Update Baidu searchplugin with new code
Categories
(Firefox :: Search, enhancement)
Tracking
()
People
(Reporter: hectorz, Assigned: hectorz)
References
Details
Attachments
(4 files)
|
47 bytes,
text/x-phabricator-request
|
pascalc
:
approval-mozilla-beta+
lizzard
:
approval-mozilla-release+
lizzard
:
approval-mozilla-esr60+
|
Details | Review |
|
34.77 KB,
image/png
|
Details | |
|
18.03 KB,
image/png
|
Details | |
|
8.85 KB,
patch
|
Details | Diff | Splinter Review |
As previously mentioned in an email, Baidu is asking us to replace the search code "monline_dg" in vanilla desktop Firefox with a new one "monline_7_dg".
| Assignee | ||
Comment 1•7 years ago
|
||
Updated•7 years ago
|
| Assignee | ||
Comment 2•7 years ago
|
||
Comment 3•7 years ago
|
||
Comment 4•7 years ago
|
||
We'll need to request uplift for this.
Comment 5•7 years ago
|
||
Updated•7 years ago
|
Comment 6•7 years ago
|
||
I assume this would affect both Fennec and Desktop - can you confirm that?
Updated•7 years ago
|
| Assignee | ||
Comment 7•7 years ago
|
||
(In reply to Liz Henry (:lizzard) (use needinfo) from comment #6)
I assume this would affect both Fennec and Desktop - can you confirm that?
No, this is desktop only. We use a separate code for Fennec. 1
Comment 8•7 years ago
|
||
Hector, can you please request the uplift to beta and release? Thanks
| Assignee | ||
Comment 9•7 years ago
•
|
||
Comment on attachment 9054385 [details]
Bug 1540017 - Update Baidu searchplugin with new code. r=mkaply
Beta/Release Uplift Approval Request
- Feature/Bug causing the regression: N/A
- User impact if declined: Not really user facing, but continued use of the old search code has its revenue implications
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: Yes, see comment 14
- Needs manual test from QE?: No, not needed from global QE team, we’ll handle it from Beijing office
- If yes, steps to reproduce: N/A
- List of other uplifts needed: N/A
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Simple text replacement w/o any real logic change
- String changes made/needed: N/A
| Assignee | ||
Comment 10•7 years ago
|
||
Comment on attachment 9054385 [details]
Bug 1540017 - Update Baidu searchplugin with new code. r=mkaply
ESR Uplift Approval Request
- If this is not a sec:{high,crit} bug, please state case for ESR consideration: Continued use of the old search code has its revenue implications
- User impact if declined: Not really user facing, but see above
- Fix Landed on Version: 68.0
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Simple text replacement w/o any real logic change
- String or UUID changes made by this patch: N/A
| Comment hidden (obsolete) |
Comment 12•7 years ago
|
||
Comment on attachment 9054385 [details]
Bug 1540017 - Update Baidu searchplugin with new code. r=mkaply
Uplift approved for 67 beta 9, thanks.
Comment 13•7 years ago
|
||
(In reply to Hector Zhao [:hectorz] from comment #11)
Beta/Release Uplift Approval Request
- Has the fix been verified in Nightly?: No
Yes, by me, unless it has to be done by someone other than the patch author.
Yes, it needs to be verified on the affected branches by someone other than the patch author :)
Comment 14•7 years ago
|
||
I've verified the fix in Firefox Nightly 68.0a1 build 20190406214855.
Comment 15•7 years ago
|
||
| uplift | ||
| Assignee | ||
Comment 16•7 years ago
|
||
Per comment 14 & comment 15
Comment 17•7 years ago
|
||
Comment on attachment 9054385 [details]
Bug 1540017 - Update Baidu searchplugin with new code. r=mkaply
Planned change to search code, OK for uplift to m-r.
This should go into the upcoming 66.0.3 release.
Comment 18•7 years ago
|
||
Mike or Hector, can you suggest a release note?
Also, why is this confidential?
Comment 19•7 years ago
|
||
Hello,
I checked this issue and I can confirm that the issue is fixed for Fx 67.0b9 on Windows 10 x64.
Comment 20•7 years ago
|
||
| uplift | ||
| Assignee | ||
Comment 21•7 years ago
|
||
(In reply to Liz Henry (:lizzard) (use needinfo) from comment #18)
Mike or Hector, can you suggest a release note?
My first thought was to copy the note for bug 1510296, but I cannot find it. Is it necessary to explicitly relnote this change?
Also, why is this confidential?
It was mostly me being cautious, in case we need to discuss more details about the abovementioned revenue implications.
Comment 22•7 years ago
|
||
After double checking with mkaply, noting this for 66.0.3 as "Updated Baidu search plugin"
Comment 23•7 years ago
•
|
||
Hello,
I noticed something strange, (on 66.0.3 zh-CN) when searching from the Firefox starting page the search url displays monline_3_dg not monline_7_dg. I will attach a screenshot with the url.
Also I checked the address bar, awesome bar, the context menu search and the new tab search and they all returned monline_7_dg.
Is this behavior intended?
Comment 24•7 years ago
|
||
| Assignee | ||
Comment 25•7 years ago
|
||
(In reply to Daniel Cicas [:dcicas], Release QA from comment #23)
Hello,
I noticed something strange, (on 66.0.3 zh-CN) when searching from the Firefox starting page the search url displays monline_3_dg not monline_7_dg. I will attach a screenshot with the url.
Also I checked the address bar, awesome bar, the context menu search and the new tab search and they all returned monline_7_dg.
Is this behavior intended?
Yes, this is intended.
In zh-CN build, homepage defaults to a webpage 1, and we're using the search code monline_3_dg there. If an user opts to use about:home as their homepage, the Baidu search code should be updated to the new monline_7_dg.
Comment 27•7 years ago
|
||
Hello,
I verified and can confirm that this issue is fixed for Fx 66.0.3 on Windows 10 x64, Ubuntu 18.14 and mac OS 10.14.
| Assignee | ||
Updated•7 years ago
|
Comment 28•7 years ago
|
||
Comment on attachment 9054385 [details]
Bug 1540017 - Update Baidu searchplugin with new code. r=mkaply
OK for uplift for 60.7.0esr.
| Assignee | ||
Comment 30•7 years ago
|
||
(In reply to Ryan VanderMeulen [:RyanVM] from comment #29)
This needs a rebased patch for ESR60.
Please see this attachment.
Comment 31•7 years ago
|
||
| bugherder uplift | ||
Comment 32•7 years ago
|
||
Looks like the rebased patch got landed, so clearing NI.
Comment 33•7 years ago
|
||
Hello,
I can confirm that this issue is fixed on Fx 60.7.0 esr.
Description
•