908082 - [B2G][Helix][Browser][chenhoulai]Editing a bookmark in the browser address, set it to null or wrong address,Save and then can not be edited or remove the address

Status: RESOLVED WONTFIX

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

Description

[lecky]

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E)

Steps to reproduce:

Editing a bookmark in the browser address, set it to null or wrong address


Actual results:

Save and then can not be edited or remove the address


Expected results:

Save and then can  be edited or remove the address

Comment 1

[lecky]

hi,jason,let me clarify the issue

Steps to reproduce:

Editing a bookmark in the browser address, set it to empty address or wrong address,eg:aaaaaa.com


Actual results:

The bookmark can be Saved,but then it becomes not be editable,not removable.

Expected results:

If such modification to bookmark is not allowed,saving operation should not be allowed.

If saving operation is performed,then the user should be allowed to edit it or remove it.

Comment 2

[lecky]

hi,jason 

in gaia\apps\browser\js\browser.js  

  saveBookmark: function browser_saveBookmark() {
    var url = this.bookmarkUrl.value;
    var title = this.bookmarkTitle.value;
    var previousUrl = this.bookmarkPreviousUrl.value;
      //here should return when url is null and remind the user
      if (url == '') {
        document.getElementById("tip_bookmark_url").style.visibility="visible";
          return;
      }
 }

Comment 3

[lecky]

hi,wayne,

could you check this issue,can it be fixed on V1.1?

Comment 4

[Dale Harvey (:daleharvey)]

Cant find a dupe for this either, confirmed the bug exists though, definitely sprint ready

Comment 5

[Wayne Chang [:wchang]]

I am bumping this to koi?... its observed on other 1.1 devices as well.

User impact : the bookmarks with incorrect addresses are not editable or removable, basically permanently leaving a non-functional link and user sees this each time browser is launched.

However, considering users will mostly visit a site and then bookmark it rather than entering an address manually, I dont see this as a critical blocker for v1.1.

Comment 6

[lecky]

hi Beatriz:
  Would you agree this issue not to fix on 1.1?

Comment 7

[Beatriz Rodríguez [:brg]]

(In reply to lecky from comment #6)
> hi Beatriz:
>   Would you agree this issue not to fix on 1.1?
Agree with comment 5.

Comment 8

[BMO Automation]

Firefox OS is not being worked on