Exposing methods required by capturing a hidden webContents

Editor assessment

The subject's gerund opening and vague phrasing, Exposing methods required by capturing a hidden webContents, leave unclear which methods were exposed, what capturing entails, and why the API surface needed extension. The feat type is right for new methods. No scope identifies the webContents area, no body enumerates the additions or the capture use case, and no footers appear. Hygiene suffers from the non-imperative construction and the capitalization, though the latter is permitted. Understandable in outline, but the message forces the reader to the diff for every specific.