14196 – External interface violates member naming conventions

This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14196 - External interface violates member naming conventions

Summary: External interface violates member naming conventions

Status:	CLOSED WONTFIX

Alias:	None

Product:	HTML WG
Classification:	Unclassified
Component:	HTML5 spec (show other bugs)
Version:	unspecified
Hardware:	All All

Importance:	P2 normal
Target Milestone:	---
Assignee:	Ian 'Hixie' Hickson
QA Contact:	HTML WG Bugzilla archive list

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2011-09-18 02:00 UTC by Glenn Adams
Modified:	2011-10-19 23:50 UTC (History)
CC List:	4 users (show)

See Also:

Attachments

Description Glenn Adams 2011-09-18 02:00:56 UTC

The 'External' interface defines two methods:

* AddSearchProvider
* IsSearchProviderInstalled

For consistency with the extant naming conventions, these should be changed to:

* addSearchProvider
* isSearchProviderInstalled

Comment 1 Ian 'Hixie' Hickson 2011-10-19 23:22:57 UTC

EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: AddSearchProvider() is a legacy interface. Within the interface, consistency amongst members seems more important than consistency with the rest of the platform.

Comment 2 Glenn Adams 2011-10-19 23:50:12 UTC

(In reply to comment #1)
> EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
> satisfied with this response, please change the state of this bug to CLOSED. If
> you have additional information and would like the editor to reconsider, please
> reopen this bug. If you would like to escalate the issue to the full HTML
> Working Group, please add the TrackerRequest keyword to this bug, and suggest
> title and text for the tracker issue; or you may create a tracker issue
> yourself, if you are able to do so. For more details, see this document:
>    http://dev.w3.org/html5/decision-policy/decision-policy.html
> 
> Status: Rejected
> Change Description: no spec change
> Rationale: AddSearchProvider() is a legacy interface. Within the interface,
> consistency amongst members seems more important than consistency with the rest
> of the platform.

I've closed this, but it would still be useful to add a comment/note in the text indicating that the reason for the variance in naming is due to considerations of backward compatibility with existing usage.