Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ids not generated for hidden inputs #48

Closed
bazo opened this issue Nov 18, 2014 · 7 comments
Closed

ids not generated for hidden inputs #48

bazo opened this issue Nov 18, 2014 · 7 comments

Comments

@bazo
Copy link

bazo commented Nov 18, 2014

in latest dev-master, hidden inputs have no html ids.

before we had e.g. frm-documentEditor-form-items now there's nothing

is this a bug or a new feature? it breaks all legacy js that works with these generated ids in our app

would suck big time to hunt down all hidden fields that are being used somewhere in js and manually change them

@dg
Copy link
Member

dg commented Nov 18, 2014

To look in history https://github.com/nette/forms/commits/master/src/Forms/Controls/HiddenField.php is probably faster that to create this issue.

It is experimental.

@vojtech-dobes
Copy link
Contributor

Once again it becomes clear that dependency on generated IDs is good candidate for refactoring :).

@vysinsky
Copy link

Once again it becomes clear that dependency on generated IDs is good candidate for refactoring :).

👍

@bazo
Copy link
Author

bazo commented Nov 18, 2014

well, tell to that guy who coded that before me :) refactoring is best done one step at a time, not all at once

btw, what's the reason for this change? i don't think it helps anything or that it would be problematic. it's just harmless and i would guess there would more apps out there that depend on it

i'm for keeping it, like it was in 2.2

@bazo
Copy link
Author

bazo commented Nov 18, 2014

btw, $form['items']->getHtmlId() still returns the generated id, shouldn't it return NULL then?

@mishak87
Copy link
Contributor

@bazo Did that guy also decided to migrate code instead to next stable to @dev again or was that you?

@bazo
Copy link
Author

bazo commented Nov 19, 2014

and how is that relevant? that was an answer to vojtech. i've already fixed that.
but i'm just asking what advantage this change has?

@dg dg closed this as completed Feb 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants