Hi
not sure what is the background and what you are trying to accomplish, however I don't think that the t:formdata value is a customization contract point. That is, we do not support customizations that rely on using that value directly.
What I suggest is to get in contact with Support and try to determine what is the real reason for your issue, which seems to be that your mobile search feature does not work.
Thanks,
PaoloT , this is the issue that forced me to use the static code for the search input:
In short, the input type is incorrect on the mobile search component. It should be type = "search". Can this issue be fixed on the Lithium side? If so, then I can look into using the default mobile component. If not, perhaps you have a workaround so that the changing T-value doesn't break our current code?
- Alan
Instead of trying to directly trying to change the 'type' attribute via jQuery, have you tried replacing the input element alltogether (with jQuery)?
I had a quick experiment, and this seems to work for me:
$('.lia-component-search-widget-simple-search-form div.lia-form-input-wrapper').innerHTML = '<input class="lia-form-all-words-input lia-form-type-text lia-form-input-vertical" id="lia-allWords_0" name="allWords" type="search">'You also need to create some CSS rules for the input[type=search] that replicate the input[type=text] rules.
Hi iftomkins
my assessment is that it sounds a bit overkill to replace completely the search component for what seems to be a cosmetic issue (i.e. "Go" vs "Search" wording on the iPhone).
If this is an issue that needs resolving, then my assessment is the same as the last time, that is to build a custom search component. If this is done, it should be achieved via our standard customization points (that is, REST APIs and in particular I would suggest to leverage LiQL which has been added since I wrote my original reply there).
Playing with t:formdata directly unfortunately is not supported.
I hope this gives you some pointers on how to proceed!
Thanks,
