Closed Bug 1207049 Opened 9 years ago Closed 6 years ago

previous URL shows on pin site section if ever opened a webpage which has defined name in manifest or application-name

Categories

(Firefox OS Graveyard :: Gaia::Browser, defect, P2)

ARM
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: ashiue, Unassigned)

References

()

Details

(Whiteboard: [systemsfe])

STR:
1. Go to a website which does have defined name in manifest or application-name
2. Tap overflow menu->Pin, and go to pin site section
3. Go to another website which does not define name in manifest or application-name
4. Tap overflow menu->Pin, and go to pin site section

Expected result:
1. Information shows correctly

Actual result:
1. URL opened from step 1 shows

Build info:
[Flame]
Build ID           	20150921150203
Gaia Revision      	29991414eb94b6baa1ec2e63fdb4f6dfae05fb01
Gaia Date          	2015-09-21 09:27:10
Gecko Revision     	https://hg.mozilla.org/mozilla-central/rev/197af2fb7e29ff8e4b3b6ced723b6172e954e17d
Gecko Version      	44.0a1
Device Name        	flame
Firmware(Release)  	4.4.2
Firmware(Incremental)  eng.cltbld.20150921.204223
Firmware Date      	Mon Sep 21 20:42:40 EDT 2015
Bootloader         	L1TC000118D0

[Aries]
Build ID           	20150921174442
Gaia Revision      	29991414eb94b6baa1ec2e63fdb4f6dfae05fb01
Gaia Date          	2015-09-21 09:27:10
Gecko Revision     	https://hg.mozilla.org/mozilla-central/rev/197af2fb7e29ff8e4b3b6ced723b6172e954e17d
Gecko Version      	44.0a1
Device Name        	aries
Firmware(Release)  	4.4.2
Firmware(Incremental)  eng.worker.20150921.170449
Firmware Date      	Mon Sep 21 17:04:57 UTC 2015
Bootloader         	s1
[Blocking Requested - why for this release]:
Obvious error
blocking-b2g: --- → 2.5?
QA Whiteboard: [COM=Pin the Web]
Blocking the feature bug for now.
Blocks: pin-the-web
blocking-b2g: 2.5? → ---
Whiteboard: [systemsfe]
Priority: -- → P2
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.