https://issues.apache.org/ooo/show_bug.cgi?id=114416
--- Comment #12 from hanya <[email protected]> --- Created attachment 81008 --> https://issues.apache.org/ooo/attachment.cgi?id=81008&action=edit Proposed patch to be determined without control-implementation attribute for value-range The result of type detection of the form control should be put into m_sServiceName instance variable. (So, this problem is happen on other kind of controls also?) To avoid the problem written in Comment 6, the empty parent form element passed when form:form element does not specify form:control-implementation attribute, OFormImport::determineDefaultServiceName returns default name of the form component. As side note: If form:control-implementation contains unknown name for AOO, the control can not be created. As described in 19.258 form:control-implementation of ODF 1.2 specification: >If the consumer supports the form element this attribute is used with, > but does not support the specific concrete rendition or implementation, > the consumer shall ignore the form:control-implementation attribute and > use its own rendition of the form element. Some fall back should be provided for unknown name. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
