Skip to main content

Bug Tracker

Side navigation

#9949 closed bug (invalid)

Opened August 01, 2011 01:43PM UTC

Closed August 16, 2011 07:45AM UTC

expr.replace is not a function

Reported by: boraz Owned by: boraz
Priority: low Milestone: None
Component: manipulation Version: 1.6.2
Keywords: Cc:
Blocked by: Blocking:
Description

this the line indicated by firebug:

expr = expr.replace(/\\=\\s*([^'"\\]]*)\\s*\\]/g, "='$1']");

here is the code which causes the error, notice that this code have been working untill last friday, i didn't change jquery version, the code got broken with no apparent reason.

here i get two html select and their labels

var inStock = $('#selectedStore');

var stockLabel = $(inStock).prev("label");

var inProducer = $('#selectedProducer');

var producerLabel = $(inProducer).prev("label");

here i get the html div which contains the selects and labels

var div = $(inStock).parent('div');

// here i remove one of the two label/select pair because i need to palce it after the other

div.remove(inStock); this line gives error, but it didn't few days ago, it always worked

div.remove(stockLabel);

here i place the objects after the element i want

$(inProducer).after(stockLabel);

$(stockLabel).after(inStock);

the code is not working also on chrome and ie.

Attachments (0)
Change History (2)

Changed August 01, 2011 01:49PM UTC by timmywil comment:1

component: unfiledmanipulation
owner: → boraz
priority: undecidedlow
status: newpending

Thanks for taking the time to contribute to the jQuery project! Please provide a reduced test case on http://jsfiddle.net that reproduces the issue experienced to help us assess your ticket.

Additionally, test against the jQuery (edge) version to ensure the issue still exists.

Changed August 16, 2011 07:45AM UTC by trac-o-bot comment:2

resolution: → invalid
status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!