Closed (fixed)
Project:
Translation Management Tool
Version:
8.x-1.x-dev
Component:
Translator: Local
Priority:
Normal
Category:
Bug report
Assigned:
Issue tags:
Reporter:
Created:
21 Jan 2016 at 09:15 UTC
Updated:
9 Feb 2016 at 22:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
edurenye commentedDone, here you can see the result:
Comment #3
miro_dietikerThat looks pretty well.
Is this really an else - so the max length is not validated if we have a format?
I would expect that both is possible at the same time.
Comment #4
miro_dietikerOK discussed, will be a followup to check source plugins and support both max length and format at the same time if needed.
Still we need test coverage to check consideration of format.
Comment #5
edurenye commentedAdded the tests, this should fail when adding a translation to the second data item without this fix, would be better to assert ussing class but we can not do that in simpletest until this issue is not finished #2469713: Step 2: Create a JavaScriptTestBase using PhantomJs Driver/Binary.
Should I add a @todo, I think is not necessary if the test_only fails, but not sure.
Comment #6
edurenye commentedI'll make this test fail.
Created the followup #2654970: Check source length limits on formatted text fields.
Comment #7
edurenye commentedThat was completely wrong, so I fixed and added proper tests.
I'm not sure that now it's ok, because of the force option in the NestedArray::setValue in LocalTaskItem, but without I have some errors.
With this the tests pass and I tested manually and seems that everything is working fine.
Comment #10
edurenye commentedReverted the change in Data.
Comment #12
miro_dietikerLong live format support! Committed! :-)