Details
Bug
Major
Description
Seems innocuous, but it's already come up a couple of times in the forum and in
our own projects. If you have a <f:param name="id" value=".."/> on your
page, the js blows up when looking for other .id properties. Perhaps we could
watch for this on parsing pages (or in the <ice:menu> or <ice:commandLink>
component handlers) and log an ERROR or WARNING.
our own projects. If you have a <f:param name="id" value=".."/> on your
page, the js blows up when looking for other .id properties. Perhaps we could
watch for this on parsing pages (or in the <ice:menu> or <ice:commandLink>
component handlers) and log an ERROR or WARNING.
Activity
yes, but let's please not talk about semantics
Show
Philip Breau
added a comment - yes, but let's please not talk about semantics
Is this a general problem for all components?
Show
Ted Goddard
added a comment -
Is this a general problem for all components?
AFAIK, any components that can use an <f:param>, which includes only the
<ice:commandLink> I believe, and the <ice:menu> (coming) as I mentioned. Is that
right Greg?
Show
Philip Breau
added a comment - AFAIK, any components that can use an <f:param>, which includes only the
<ice:commandLink> I believe, and the <ice:menu> (coming) as I mentioned. Is that
right Greg?
I believe this issue was fixed in rev.#10728 of submit.js
(Make 'iceSubmit' function more robust)
Having a param named "id" will nolonger break the ice submit functions.
It still may be worthwhile to log a warning at parse time.
Show
Greg McCleary
added a comment - I believe this issue was fixed in rev.#10728 of submit.js
(Make 'iceSubmit' function more robust)
Having a param named "id" will nolonger break the ice submit functions.
It still may be worthwhile to log a warning at parse time.
The fix delivered earlier is now in the head; please verify that the customer's application is fixed with
today's build.
Show
Ted Goddard
added a comment -
The fix delivered earlier is now in the head; please verify that the customer's application is fixed with
today's build.
Philip,
Was this issue fixed in v1.5. Please mark the case Resolved Fixed if so.
| Field | Original Value | New Value |
|---|---|---|
| issue.field.bugzillaimportkey | 950 | 12200 |
| Affects Version/s | 1.5 [ 10027 ] | |
| Affects Version/s | 1.0.1 [ 10025 ] |
| Summary | JS erros occurs when using an <f:param name="id"... | JS error occurs when using an <f:param name="id"... |
| Description |
Seems innocuous, but it's already come up a couple of times in the forum and in the Williams project. If you have a <f:param name="id" value=".."/> on your page, the js blows up when looking for other .id properties. Perhaps we could watch for this on parsing pages (or in the <ice:menu> or <ice:commandLink> component handlers) and log an ERROR or WARNING. |
Seems innocuous, but it's already come up a couple of times in the forum and in our own projects. If you have a <f:param name="id" value=".."/> on your page, the js blows up when looking for other .id properties. Perhaps we could watch for this on parsing pages (or in the <ice:menu> or <ice:commandLink> component handlers) and log an ERROR or WARNING. |
fixed, verified with 1.5.3
Show
Philip Breau
added a comment - fixed, verified with 1.5.3
| Status | Open [ 1 ] | Closed [ 6 ] |
| Fix Version/s | 1.5.4 [ 10034 ] | |
| Fix Version/s | 1.6 [ 10031 ] | |
| Resolution | Fixed [ 1 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Closed [ 6 ] | Reopened [ 4 ] |
| Fix Version/s | 1.5.3 [ 10030 ] | |
| Fix Version/s | 1.5.4 [ 10034 ] |
| Status | Reopened [ 4 ] | Closed [ 6 ] |
| Resolution | Fixed [ 1 ] |
Is the problem that the "name" is specifically "id"?