Obsolete
Status Update
Comments
ma...@gmail.com <ma...@gmail.com> #2
Restricting support to the most basic HTML tags would be fine with me.
jo...@gmail.com <jo...@gmail.com> #3
Hi,
During development of my project I come across some tags which is listed below.
1. <a href="...">
2. <b>
3. <i>
4. <img src="...">
5. <p>
I hope some other post what they got in their box so everyone knows the exact.
Thanks for starting truly useful thread here.
During development of my project I come across some tags which is listed below.
1. <a href="...">
2. <b>
3. <i>
4. <img src="...">
5. <p>
I hope some other post what they got in their box so everyone knows the exact.
Thanks for starting truly useful thread here.
jo...@gmail.com <jo...@gmail.com> #4
There are 10+ threads on stackoverflow asking this question all referring to http://commonsware.com/blog/Android/2010/05/26/html-tags-supported-by-textview.html as the inofficial list.
Google, care to answer this question?
Google, care to answer this question?
[Deleted User] <[Deleted User]> #5
Hi i am using tag in text view as follows:
textViewobj.setText(Html.fromHtml("<font size=\"40\" face=\"arial\" color=\"red\">ggg</font><br><br>"));
It makes the text red but neither size attribute works nor face works.
Please make the font usage more clear in documentation we are really struggling with this issue.
Actually i want to show html formatted text in email intent. There is no way achieve this but to use fromHtml().
textViewobj.setText(Html.fromHtml("<font size=\"40\" face=\"arial\" color=\"red\">ggg</font><br><br>"));
It makes the text red but neither size attribute works nor face works.
Please make the font usage more clear in documentation we are really struggling with this issue.
Actually i want to show html formatted text in email intent. There is no way achieve this but to use fromHtml().
ia...@gmail.com <ia...@gmail.com> #6
From the source at http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android/2.2_r1.1/android/text/Html.java it would appear that <font> supports color and face but NOT size.
It would appear that face can be specified as one of the installed fonts sans, serif, or monospace, or defaulted to an additional font specifed by the setTypeface() method.
It would appear that face can be specified as one of the installed fonts sans, serif, or monospace, or defaulted to an additional font specifed by the setTypeface() method.
an...@gmail.com <an...@gmail.com> #7
[Comment deleted]
ja...@gmail.com <ja...@gmail.com> #8
[Comment deleted]
jb...@android.com <jb...@android.com> #10
[Comment deleted]
jb...@android.com <jb...@android.com> #11
[Comment deleted]
bi...@gmail.com <bi...@gmail.com> #12
The HTML tag <em> does not work properly.
It is supposed to generate an 'em' space. Instead, it appears to change the font to Italic.
However, the string ' ' does generate an em space where needed.
It is supposed to generate an 'em' space. Instead, it appears to change the font to Italic.
However, the string ' ' does generate an em space where needed.
gu...@gmail.com <gu...@gmail.com> #13
You should learn HTML, <em> is supposed to change the font to italic (http://www.w3schools.com/tags/tag_em.asp )
da...@gmail.com <da...@gmail.com> #14
4 years since reporting, any news Google? :)
[Deleted User] <[Deleted User]> #16
Doesn't look like it received any updates in the L release either. Still no bullet or numbered list support.
da...@gmail.com <da...@gmail.com> #17
I know how to see which tag are supported in code.
This bug is open for another reason: code is not a specification.
Assuming the code will not change or that those tags will always be supported is risky.
Furthermore if you really want to look at the code you should check that for every released version of Android and hope no manufacturer changed it in their custom Android release.
This bug is open for another reason: code is not a specification.
Assuming the code will not change or that those tags will always be supported is risky.
Furthermore if you really want to look at the code you should check that for every released version of Android and hope no manufacturer changed it in their custom Android release.
ch...@orr.me.uk <ch...@orr.me.uk> #18
Well, arguably the code in AOSP is a specification, but adding documentation is no guarantee against manufacturers making changes in their own builds.
If somebody really wants to fix this, the Javadoc for this method should be extended to include the supported HTML tags and attributes, then the *CTS should be extended* to cover all of the supported markup:
https://android.googlesource.com/platform/cts/+/master/tests/tests/text/src/android/text/cts/HtmlTest.java
If somebody really wants to fix this, the Javadoc for this method should be extended to include the supported HTML tags and attributes, then the *CTS should be extended* to cover all of the supported markup:
nj...@gmail.com <nj...@gmail.com> #19
Another year and now we're at "M" - anything yet?
lb...@gmail.com <lb...@gmail.com> #20
Anyone knows which font-faces are available when using the "font" tag? I can't find this documented anywhere.
zh...@gmail.com <zh...@gmail.com> #21
the common attribute like align and style is still not support?
nj...@gmail.com <nj...@gmail.com> #22
It was also hard to figure out if font tag, face attribute was supported, in what way if at all size was supported, leave px off, use <smaller>, or what...
ha...@gmail.com <ha...@gmail.com> #23
si...@google.com <si...@google.com> #24
This bug has not been modified within the last 365 days. If this bug is still valid, please reopen with a current bugreport and repro steps.
Description
from the provided HTML string." However, it does not state what HTML tags
are supported, meaning that we as developer cannot rely on this method
doing anything specific from release to release.
While we can reverse-engineer a roster of tags from the source code, until
and unless Google commits to a roster of tags that it will support, we are
just hoping this stuff will work over time. As is evidenced by the
undocumented Calendar content provider (and various blog posts, including
some from yours truly), we cannot rely upon undocumented behavior.
Please add a roster of supported tags to the documentation, so we know what
will work "out of the box" and what we may have to write our own tag
handler for (or just simply avoid).
Thanks!