Gazal
Gazal
@fabi1cazenave by a quick function, I'm assuming you mean an imperative mechanism to apply localization instead of on DOM getting ready. Is such a function present in the current API?
Looks like I found it: `document.webL10n.translate(element)` does the trick for me
for a single page application with a lot of DOM changes though, webL10n does not truly give declarative localization. Mutation Observers may be the answer.
@n1k0 this works for me: `_` - lodash ``` js document.addEventListener('localized', function() { var observer = new MutationObserver(function(mutations) { _.forEach(_.pluck(mutations, 'target'), function(element) { document.webL10n.translate(element); }); }); observer.observe(document.body, { childList: true,...
Actually I did test both snippets in an application. The first one does trigger the MO callback an extra time after the translation, but a subsequent call to translate does...
Sorry, I'm not really familiar with the selenium grid codebase. I imagine this: https://github.com/SeleniumHQ/selenium/blob/trunk/java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java has some of the logic to dynamically create browser nodes to join the grid. It would...
@NiQDeveloper, you may wanna watch this issue
Hey @bcoe, we'd like to contribute to this feature if it is worth having
Yes, I had the same discussion with @NiQDeveloper and he did mean to compare `json-summary` to the `text` report. They both have coverage reported per source file as opposed to...