If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

parsing xml with xslt truncates strings in <div> and <textarea> elements to 4096 bytes

RESOLVED INCOMPLETE

Status

()

Core
XSLT
--
major
RESOLVED INCOMPLETE
12 years ago
9 years ago

People

(Reporter: rorschach, Unassigned)

Tracking

Trunk
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

I have an xml with text nodes larger than 4096 bytes. These textnodes are
truncated to 4096 bytes when i transform them them to appear inside xhtml <div>
and <textarea> elements. The texts have the original size when I view them in
view-source, so the error should lie in the xslt-parser.

Reproducible: Always
(Reporter)

Comment 1

12 years ago
(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10)
Gecko/20050716 Firefox/1.0.6
> Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10)
Gecko/20050716 Firefox/1.0.6
> 
> I have an xml with text nodes larger than 4096 bytes. These textnodes are
> truncated to 4096 bytes when i transform them them to appear inside xhtml <div>
> and <textarea> elements. The texts have the original size when I view them in
> view-source, so the error should lie in the xslt-parser.
> 
> Reproducible: Always

By the way, when generating xhtml with an external xslt-parser (saxon) and
viewing the html, the texts are not truncated. The problem should lie with the
xslt-parser used.
Assignee: nobody → peterv
Component: General → XSLT
Product: Firefox → Core
QA Contact: general → keith
Version: unspecified → Trunk

Comment 2

12 years ago
Duplicate of/related to bug 194231?
Please attach a testcase. It probably depends on how you get the data in the <div>.

But yeah, this is most likly caused by bug 194231. Though we could fix it on the
transformiix side. And we sort of need to since the same situation could arrise
through DOM modifications.
Depends on: 194231
Is this bug still valid? Reporter, can you attach a testcase which reproduces this bug?

3 years untouched, unconfirmed bug.
Resolving as incomplete for now due to the missing testcase, please reopen when you can provide one.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
Assignee: peterv → nobody
No longer depends on: 194231
QA Contact: keith → xslt
You need to log in before you can comment on or make changes to this bug.