Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 255702

Summary:	failed to interpret the Start tag <p>
Product:	[WebTools] WTP Source Editing	Reporter:	Kathy Miao <kmiao>
Component:	wst.html	Assignee:	Nick Sandonato <nsand.dev>
Status:	CLOSED DUPLICATE	QA Contact:	Nitin Dahyabhai <thatnitind>
Severity:	normal
Priority:	P3	CC:	edwinc, jerome_lanneluc, nsand.dev
Version:	3.0
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Kathy Miao

2008-11-18 14:51:07 EST

Build ID: eclipse.buildId=3.4.0

Steps To Reproduce:
1.This is a defect found on a product that build on eclipse 
2. The error complains "No Start tag (<p>)" for a html file, but in that file, we do have the start tag. 
3. please contact me at kmiao@ca.ibm.com for detail artifacts. 

Thanks, 
Kathy Miao


More information:

Comment 1 Jerome Lanneluc

2008-11-19 04:23:47 EST

Could you please give more details on why you think this is a JDT/Core bug?
If you're using a product build on Eclipse, the problem might be in the code of the product.

Comment 2 Kathy Miao

2009-01-21 09:37:20 EST

Artifact has been sent to jerome_lanneluc@fr.ibm.com for investigate.

Comment 3 Jerome Lanneluc

2009-01-21 09:40:07 EST

Still need to know what you (or your customer) were doing at the time you got the error? I.e. I have no clue what I should do with the file you sent me.

Comment 4 Kathy Miao

2009-01-21 09:58:25 EST

We imported the customer PI and found this error in problem view, we did not do anything else. I've asked our developers, and get the answer: 

This error message comes from an org.eclipse.wst validator. That's the component where the bugzilla defect should go to.
It should be sufficient to send them the HTML file (plus included CSS and JS files if needed).

Comment 5 Jerome Lanneluc

2009-01-21 10:32:13 EST

Thanks. Moving to WST then.

Comment 6 Nick Sandonato

2009-01-21 10:57:53 EST

This sounds like an HTML Validation problem. It may potentially be a duplicate of bug 223942. If you could provide a sample file that produces the problem, it would help me in diagnosing the issue.

Comment 7 Kathy Miao

2009-01-21 11:20:30 EST

Hi Nick, 
Just forward the artifacts to you through e-mail. 

Regards, 
Kathy

Comment 8 Nick Sandonato

2009-12-08 15:47:44 EST

This was resolved in 3.2 since we no longer promote invalid child elements in the DOM. Instead, the user will now see an "Invalid location of tag (p)." message, which is more useful.

Please see bug 283840.

*** This bug has been marked as a duplicate of bug 283840 ***