Skip to content

Bug when only destination for ID and not value is defined #11

@sd5000

Description

@sd5000

Found a little bug, I think. When invoking the component I only had the destinationForSelectedId attribute defined and did not have destinationForSelectedValue defined. That used to work fine but at some point must have stopped working. It was bonking on line 137 in Typeahead.component, throwing the error "Syntax error, unrecognized expression: [id$=]" due to the blank destinationForSelectedValue attribute:

135 // if destinations are defined, set them too
136 j$('[id$={!destinationForSelectedId}]').val( id );
137 j$('[id$={!destinationForSelectedValue}]').val( value );

I fixed my issue by adding the destinationForSelectedValue attribute to the component call but wanted to let you know. Can't quite figure out why it used to work and stopped at some point.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions