Closed
Bug 40458
Opened 25 years ago
Closed 9 years ago
need to verify that Composer handles all known html elements
Categories
(Core Graveyard :: Tracking, defect, P1)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
Future
People
(Reporter: rubydoo123, Unassigned)
Details
(Whiteboard: [nsbeta3-])
Attachments
(6 files)
supply a test case with all known html elements -- except
frame/frameset/noframes
|
Reporter | |
Comment 1•25 years ago
|
||
|
|
Reporter | |
Updated•25 years ago
|
Target Milestone: --- → M17
|
||
Comment 3•25 years ago
|
||
ack. sorry beth, I just remembered you wanted me to look into the testcase.
Sorry, somehow I forgot to do it. Will do it now...
|
||
Comment 5•25 years ago
|
||
even in 4.74, the browser lays out the rest of the page in plaintext when it
reaches the <plaintext> element. odd. will attach a simple html test file with
only <plaintext> in it (well, other than the usual <html><body> </body></html>
elements).
|
|
||
Comment 6•25 years ago
|
||
just realized i was being vague there... i meant to say that i tried out the
attached test case from 5/24 in communicator 4.74, and the layout stopped
working after the <plaintext> element was encountered. ie, all content after
that element was displayed as plain text, even though there's a closing tag for
that element. odd.
anyhow, i tried loading the same test case in today's linux commercial build,
2000.07.14.08, and it crashed. talkback #14170240 trace:
nsKeygenFormProcessor::ProvideContent()
CNavDTD::HandleKeyGen()
CNavDTD::HandleStartToken()
CNavDTD::HandleToken()
CNavDTD::BuildModel()
nsParser::BuildModel()
nsParser::ResumeParse()
nsParser::OnDataAvailable()
nsDocumentOpenInfo::OnDataAvailable()
nsHTTPFinalListener::OnDataAvailable()
InterceptStreamListener::OnDataAvailable()
nsHTTPChunkConv::OnDataAvailable()
nsHTTPServerListener::OnDataAvailable()
nsOnDataAvailableEvent::HandleEvent()
nsStreamListenerEvent::HandlePLEvent()
PL_HandleEvent()
PL_ProcessPendingEvents()
nsEventQueueImpl::ProcessPendingEvents()
event_processor_callback()
our_gdk_io_invoke()
libglib-1.2.so.0 + 0xeaca (0x404b0aca)
libglib-1.2.so.0 + 0x10186 (0x404b2186)
libglib-1.2.so.0 + 0x10751 (0x404b2751)
libglib-1.2.so.0 + 0x108f1 (0x404b28f1)
libgtk-1.2.so.0 + 0x8c5b9 (0x403d75b9)
nsAppShell::Run()
nsAppShellService::Run()
main1()
main()
libc.so.6 + 0x189cb (0x402469cb)
not sure what part of the test case is at fault for this, though...
|
|
||
Comment 7•25 years ago
|
||
anyhow, returning to my first comment in this bug, i tried out my simple test
(will attach soon), and as in 4.74, mozilla displays the page as plaintext once
it enounters the element.
|
|
||
Comment 8•25 years ago
|
||
|
|
Reporter | |
Comment 9•25 years ago
|
||
setting component and whiteboard to tracking
Component: Editor → Tracking
Whiteboard: [TRACKING]
|
|
Reporter | |
Comment 10•24 years ago
|
||
I need to run the test cases again to ensure that Composer handles all valid
HTML elements
|
||
Comment 11•24 years ago
|
||
Running testcases is great, but we don't need an nsbeta3+ bug to do that. Please
file bugs on any serious errors you find as a result of testing. Marking nsbeta3-
Whiteboard: [nsbeta3+] → [nsbeta3-]
|
||
Comment 14•24 years ago
|
||
unsetting the tvf... who will do this and when?
Target Milestone: mozilla0.9.1 → ---
|
|
Reporter | |
Comment 15•24 years ago
|
||
this is put into every milestone to remind us to test all of the elements,
resetting to 9.1
Target Milestone: --- → mozilla0.9.1
|
|
Reporter | |
Comment 16•24 years ago
|
||
9.2
Status: ASSIGNED → NEW
Target Milestone: mozilla0.9.1 → mozilla0.9.2
|
||
Comment 17•24 years ago
|
||
This morning's builds had a bug ( bug 80746 ) which may have led to
a Bugzilla user inadvertantly
changing this bug from the Assignbed/Accepted status to the New status. If you
are the owner of this bug please check to see that it is in the correct Status.
Thanks.
|
|
Reporter | |
Updated•24 years ago
|
Status: NEW → ASSIGNED
|
|
Reporter | |
Comment 18•24 years ago
|
||
breaking the test case out into 2 testcases: 1. test case with all elements
listed in the 4.01 DTD, 2. other elements that are either obsoleted, or
extension elements
|
|
Reporter | |
Comment 19•24 years ago
|
||
|
|
Reporter | |
Comment 20•24 years ago
|
||
|
|
Reporter | |
Comment 21•24 years ago
|
||
|
|
Reporter | |
Updated•24 years ago
|
Target Milestone: mozilla0.9.2 → mozilla1.0
|
|
Reporter | |
Comment 22•24 years ago
|
||
attaching an entities test page too
|
|
Reporter | |
Comment 23•24 years ago
|
||
|
|
||
Comment 25•23 years ago
|
||
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1
(you can query for this string to delete spam or retrieve the list of bugs I've
moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
|
||
Updated•16 years ago
|
Assignee: shrir → nobody
QA Contact: sujay → chofmann
|
||
Comment 27•9 years ago
|
||
Marking all tracking bugs which haven't been updated since 2014 as INCOMPLETE.
If this bug is still relevant, please reopen it and move it into a bugzilla component related to the work
being tracked. The Core: Tracking component will no longer be used.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
|
Assignee | |
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•