Closed Bug 1062699 Opened 10 years ago Closed 10 years ago

[NFC] Each browser tab could only share the first website

Categories

(Firefox OS Graveyard :: NFC, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:2.1+, b2g-v2.1 verified, b2g-v2.2 verified)

VERIFIED FIXED
2.1 S4 (12sep)
blocking-b2g 2.1+
Tracking Status
b2g-v2.1 --- verified
b2g-v2.2 --- verified

People

(Reporter: ashiue, Assigned: tauzen)

References

Details

Attachments

(3 files)

Gaia fbb297c39aab5f17b179533d2a9a6c5166b2c197 Gecko https://hg.mozilla.org/releases/mozilla-aurora/rev/fb5e796da813 BuildID 20140903000204 Version 34.0a2 STR: 1. Open a new website A 2. Tap an another website B on the same tab 3. Tap 2 phones together to share the URL Expect result: Receiver device receive website B Actual result: Receiver device still receive website A
[Blocking Requested - why for this release]: Obviously error
blocking-b2g: --- → 2.1?
QA Whiteboard: [COM=NFC]
Assignee: nobody → kmioduszewski
Blocks: NFC-Gaia
Attached file pull-request-1062699.txt (deleted) —
Hi Greg, can you review this? Additionally I've renamed |request| to |message| in NfcHandler to better match the NFC/NDEF terminology.
Attachment #8486348 - Flags: review?(gweng)
triage: broken function
blocking-b2g: 2.1? → 2.1+
Attachment #8486348 - Flags: review?(gweng) → review+
Keywords: checkin-needed
Status: NEW → RESOLVED
Closed: 10 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → 2.1 S4 (12sep)
Comment on attachment 8486348 [details] pull-request-1062699.txt [Approval Request Comment] [Bug caused by] (feature/regressing bug #): Bug 1039935 [User impact] if declined: Broken function, see comment 3. [Testing completed]: Unit tests passing. Tested on device, works properly. [Risk to taking this patch] (and alternatives if risky): None [String changes made]: None
Attachment #8486348 - Flags: approval-gaia-v2.1?
Comment on attachment 8486348 [details] pull-request-1062699.txt can QA please help veirfy this once it lands on 2.1. Thanks !
Attachment #8486348 - Flags: approval-gaia-v2.1? → approval-gaia-v2.1+
Keywords: verifyme
Verified on: [master] Gaia 72262d054ffa5d0d2b5a0033f713149281511aea Gecko https://hg.mozilla.org/mozilla-central/rev/4f2cac8d72da BuildID 20140917160215 Version 35.0a1 [v2.1] Gaia 379e68fe729a684fa2fcddb30ea1e65508db73e1 Gecko https://hg.mozilla.org/releases/mozilla-aurora/rev/7ff763eb328b BuildID 20140918000204 Version 34.0a2
Status: RESOLVED → VERIFIED
Attached video video of verify issue (deleted) —
This issue has been successfully verified on Flame 2.1 See attachment: verify_video.MP4 Reproducing rate: 0/5 Flame 2.1 versions: Gaia-Rev 1b231b87aad384842dfc79614b2a9ca68a4b4ff3 Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/95fbd7635152 Build-ID 20141119001205 Version 34.0 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20141119.035246 FW-Date Wed Nov 19 03:52:56 EST 2014 Bootloader L1TC00011880
Hi Kevin, please help to verify if this patch is good on master
Flags: needinfo?(kevin.tucker)
This issue is verified fixed on Flame 2.1 and Flame 2.2 Master Results: Correct website is sent to receiving device Flame 2.1 Device: Flame 2.1 (319mb)(Kitkat Base)(Shallow Flash) BuildID: 20141125001201 Gaia: 1bdd49770e2cb7a7321e6202c9bf036ab5d8f200 Gecko: db893274d9a6 Version: 34.0 (2.1) Firmware: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Flame 2.2 Device: Flame 2.2 (319mb)(Kitkat Base)(Shallow Flash) Build ID: 20141125040209 Gaia: 824a61cccec4c69be9a86ad5cb629a1f61fa142f Gecko: acde07cb4e4d Version: 36.0a1 (2.2) Firmware Version: v188-1 User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
QA Whiteboard: [COM=NFC] → [COM=NFC][QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: verifyme
QA Whiteboard: [COM=NFC][QAnalyst-Triage?] → [COM=NFC][QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Flags: needinfo?(kevin.tucker)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: