After being applied to the 8.x branch, it should be considered for backport to the 7.x branch. Note: This tag should generally remain even after the backport has been written, approved, and committed.
There are a lot of settings that are not available by default in JavaScript. E.g. the current language is not even available. This is probably done to not increase the page load for each and every page. If you need specific settings on the client side, you probably need them because you are writing a custom/contrib module that needs them. Then it is up to that custom module to add the necessary settings to the Drupal.settings object.
Comments
Comment #1
fietserwin- What date format would you like to access (all, all localized)?
- How does this request relate to #1976614: Setting jQuery UI Datepicker's dateFormat should not be translated?
Comment #2
droplet commentedthese admin/config/regional/date-time formats
Comment #3
fietserwinThere are a lot of settings that are not available by default in JavaScript. E.g. the current language is not even available. This is probably done to not increase the page load for each and every page. If you need specific settings on the client side, you probably need them because you are writing a custom/contrib module that needs them. Then it is up to that custom module to add the necessary settings to the Drupal.settings object.
So I think this is a won't fix.
Comment #4
nod_Agreed. Add that from your module if you need it, core doesn't have to include it in the default settings.