Bugzilla – Full Text Bug Listing
| Summary: | [libraries] Remove browser-specific library plug-ins | ||
|---|---|---|---|
| Product: | [WebTools] JSDT | Reporter: | Nitin Dahyabhai <thatnitind> |
| Component: | General | Assignee: | Nitin Dahyabhai <thatnitind> |
| Status: | RESOLVED WONTFIX | QA Contact: | Nitin Dahyabhai <thatnitind> |
| Severity: | normal | ||
| Priority: | P3 | CC: | david_williams |
| Version: | 3.3 | ||
| Target Milestone: | 3.4 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Nitin Dahyabhai
The IE plug-in dates back to IE6/IE7, and IE8 took over the largest share over a year ago. What were they for? Content assist? Or, some sort of "running" ability? What will happen if not there? Such as, will content assist be provided via some other mechanism? (Yes, I know, I have a short memory :) They're just stubs to provide content assist and light type information during validation. Projects would need to change their include paths to use the generic Web Browser Library (4.01 or 5 [pending bug 323211]) that we provide and actively support. If 3.3 is too soon, I could see doing this in the following version. I don't feel too strongly about it, but seems slightly better to leave the old in there for one overlapping release, so that once a user updates to 3.3 version, they don't have to update all effected projects all at once, immediately after moving to 3.3, but could schedule it in over the year, before 3.4. I don't know all angles of this, though, so (for example) if the old framework was so bad or out of date to be considered broken, then wouldn't be that bad to remove broken stuff now with clear update instructions). (As an aside, I've now updated the PMC Review document at http://wiki.eclipse.org/index.php/WTP_PMC_Defect_Review to include Chuck's name/email). Since re-targeted, I'm removing the PMC Review marks. . |