Mike Davlantes
Mike Davlantes
Seconded. This would be pretty handy for parsing empty `` fields.
Yes, a custom field could work for me but I do agree that it's rather inelegant. I ended up going with something like @anowlcalledjosh above to solve my issue. Since...
For those of us who haven't been following along the whole time, to confirm: - we can ignore any other "non-official" repos if we don't need vue3 support right now...
@marcuskelly, PR https://github.com/lingthio/Flask-User/pull/94 seems to do what you're looking for, though it was never merged. I'm not sure how it'll play with the existing code. @lingthio and @neurosnap, I second...
I have this issue as well, though my disclaimer shows up probably about 80% of the time. The other 20% of the time I get the same error message listed...
@tmcgee I'm still having the issue, but it's very sporadic. None of my users have reported it and it really only seems to come up when I'm trying to debug...
@tmcgee I just switched my content from a div with inline CSS (and a paragraph or two) to `TEST`. I haven't been able to reproduce the error like I used...
@tmcgee Yeah, I was going to give that a try but then got pulled away for a bit. I'll load my original html that way some time this afternoon and...
I just tested lazy loading my html. I was still able to get the error to occur, but it was much less frequent (48 out of 50 refreshes, or 96%,...
I'm on Chrome as well (version 45.0.2454.85 m). I haven't tested it thoroughly enough to comment on any other browsers.