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

LPS-68460 #367

Closed
wants to merge 2 commits into from
Closed

LPS-68460 #367

wants to merge 2 commits into from

Conversation

jbalsas
Copy link

@jbalsas jbalsas commented Oct 21, 2016

Hey @adolfopa,

I'm forwarding you this so you can keep track of it.

As we discussed, the fix should be applied on the Message Boards App, so this fix should be removed for a more specific one.

Thanks!

@jbalsas
Copy link
Author

jbalsas commented Oct 21, 2016

/cc @jonmak08

:octocat: Sent from GH.

@liferay-continuous-integration
Copy link
Collaborator

All tests PASSED.

Build Time: 1 hour 10 minutes 19 seconds

Base Branch:

Branch Name: master
Branch GIT ID: b4d21fb0f12508803152b7459f4e5c66e87ecc3c

Job Summary:

For more details click here.
For upstream results, click here.

@adolfopa
Copy link
Owner

Just started reviewing :)

:octocat: Sent from GH.

@BryanEngler
Copy link

@jbalsas this issue isnt just in MB. for example i think i did a test with the "password reset required" option in users admin, and that was also affected. just wanted to make sure you were aware of that

/cc @jonmak08

@jbalsas
Copy link
Author

jbalsas commented Oct 21, 2016

Hey @BryanEngler. I wasn't aware of that, and I'm pretty sure you're going to be right. Any place where we're following this pattern is likely to be affected. Could you please verify that and create a ticket for it?

However, the fact that it happens in other places, doesn't grant fixing it this way. We intentionally made this change because the previous behaviour enforces some bad html practices that we're trying to correct. The rationale for this is explained in the Breaking Changes document.

In this particular case, if I understood it correctly, we'd be creating to inputs inside a form:

  • A disabled one of type checkbox (with a different name than the one the developer configured)
  • A hidden one with the real input name and a value that won't ever be changed

We'd be creating two inputs, none of which we really need and force both the client and server side to have some additional knowledge about our taglib internals to get it right.

By staying closer to how checkboxes in forms work we can simplify both the client and the server side.

@BryanEngler
Copy link

sounds good, thanks for the info! ill create a ticket and also look to see if there are any other places where we can find the issue.

@adolfopa
Copy link
Owner

Pull request submitted to brianchandotcom#44183. See changes here.

:octocat: Sent from GH.

@adolfopa adolfopa closed this Oct 24, 2016
@jbalsas jbalsas deleted the pr-628 branch April 3, 2017 08:18
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

Successfully merging this pull request may close these issues.

4 participants