You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<customTaginline='true'>name=test_name</customTag> some text here
`HtmlWidget` configuration
Widget_htmlWidget(String string) {
returnHtmlWidget(
string,
customStylesBuilder: (element) =>_styleSheet(element),
customWidgetBuilder: (element) =>_widgetBuilder(element),
onTapUrl: _onTapUrl,
);
}
Widget?_widgetBuilder(dom.Element element) {
switch (element.localName) {
case'customTag':returnreturnInlineCustomWidget(child:InkWell(onTap: ()=>print('clicked'), child:Text('2'))); // this component is tappable and opens a dialog on tap of it using Inkwell inside.
}
returnnull;
}
Testing on chrome browser
Expected results
it should allow to tap on custom component when using InlineCustomWidget no matter what is the size of the the custom widget, it should not block tappable area of it.
Actual results
it is not allowing to tap on half of the portion of the custom component when using InlineCustomWidget no matter what is the size of the the custom widget, it blocks half of its width when coming at the start of the sentence.
The text was updated successfully, but these errors were encountered:
The expected results look reasonable. However, your issue description is missing the HTML. Also, can you provide a minimal version of component for testing?
@daohoangson Also with this custom widget builder, I am getting another issue when the HtmlWidget is wrapped with SelectionArea() widget which is shown in example of the package as well, but that makes it harder to select the text properly when you have custom widget inside the html and you start to drag horizontally.
this works fine when there is no custom widget is there in the html.
Let me know if need to raise another bug for this, but keeping it here for now because it seems related to me.
Steps to Reproduce
HTML
`HtmlWidget` configuration
Testing on chrome browser
Expected results
it should allow to tap on custom component when using
InlineCustomWidget
no matter what is the size of the the custom widget, it should not block tappable area of it.Actual results
it is not allowing to tap on half of the portion of the custom component when using
InlineCustomWidget
no matter what is the size of the the custom widget, it blocks half of its width when coming at the start of the sentence.The text was updated successfully, but these errors were encountered: