Re: Chrome complains about text input with same id

[Alex Harui]

Use localid instead of Id.

See https://issues.apache.org/jira/browse/FLEX-35310

-Alex

On 10/26/18, 12:33 PM, "Carlos Rovira" <carlosrov...@apache.org> wrote:

    Hi,
    
    I create a component in MXML that has a TextInput. Since this component is
    reusable I have it two instances in my App
    In chrome I see
    
    [DOM] Found 2 elements with non-unique id #code_ti: (More info:
    
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgoo.gl%2F9p2vKq&amp;data=02%7C01%7Caharui%40adobe.com%7C36a5c7d366b943d0c03508d63b79da97%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636761791879697771&amp;sdata=cZBkzNZJ%2Be8l%2FRqYqirImWuoHyOS9yJFZIxjpSzzUA8%3D&amp;reserved=0)
 <input type="text" id="code_ti" maxlength="5">
    
    I think there's no problem with the two components, but since chrome
    doesn't like things like this (in fact html spec wants no duplicate ids)
    
    I was trying to see how can I do. Inside my MXML I have an Script block
    that references the text input id. In fact the ID is to do that ;)
    So I can remove it, but at the same time, I'm generating html that is not
    right.
    
    So how can we deal with this? maybe our id, doesn't should be creating
    attribute id in the tag? and make the id reference in other form?
    
    Thanks
    
    -- 
    Carlos Rovira
    
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C36a5c7d366b943d0c03508d63b79da97%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636761791879697771&amp;sdata=4TEwcme3cASo5dXXFKZkqWvtg11nJ0nQzqaj9yT5hEQ%3D&amp;reserved=0