{"action":"closed","issue":{"url":"https://api.github.com/repos/tc39/ecma262/issues/514","repository_url":"https://api.github.com/repos/tc39/ecma262","labels_url":"https://api.github.com/repos/tc39/ecma262/issues/514/labels{/name}","comments_url":"https://api.github.com/repos/tc39/ecma262/issues/514/comments","events_url":"https://api.github.com/repos/tc39/ecma262/issues/514/events","html_url":"https://github.com/tc39/ecma262/issues/514","id":145415847,"number":514,"title":"String.prototype.trimStart/trimEnd (or trimLeft/trimRight)","user":{"login":"evilpie","id":296445,"avatar_url":"https://avatars.githubusercontent.com/u/296445?v=3","gravatar_id":"","url":"https://api.github.com/users/evilpie","html_url":"https://github.com/evilpie","followers_url":"https://api.github.com/users/evilpie/followers","following_url":"https://api.github.com/users/evilpie/following{/other_user}","gists_url":"https://api.github.com/users/evilpie/gists{/gist_id}","starred_url":"https://api.github.com/users/evilpie/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/evilpie/subscriptions","organizations_url":"https://api.github.com/users/evilpie/orgs","repos_url":"https://api.github.com/users/evilpie/repos","events_url":"https://api.github.com/users/evilpie/events{/privacy}","received_events_url":"https://api.github.com/users/evilpie/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-04-02T20:36:06Z","updated_at":"2016-04-19T01:14:29Z","closed_at":"2016-04-19T01:14:29Z","body":"I refreshed @sebmarkbage's trimLeft/trimRight proposal: https://evilpie.github.io/ecmascript-string-left-right-trim/. trimStart/trimEnd are now the canonical function objects, which matches the newly introduced padStart/padEnd functions. The old non-standard trimLeft/trimRight functions simply alias those. For posterity sake there is a tiny backwards compatibility issue, String.prototype.trimLeft.name would be \"trimStart\" instead of \"trimLeft\" as it is now. I don't expect this to cause any issues.\r\n\r\nI wrote up two different proposal, one where trim/trimStart/trimEnd duplicate all of the (albeit very short) code and one where those functions call an abstract operation `TrimString`. I can't actually decide, which one I like more, but the later certainly follows DRY as noted by @ljharb.\r\n\r\nThis is stage 1 proposal at the moment, so I assume I need somebody to champion this?"}}