There is an option to:
* Enable/disable accordion navigation
* Enable/disable/repoint tab navigation
This allows for full-screen XBlocks (e.g. a code IDE, or large video
player). It is also the first pass at allowing top-level XBlocks. It's
also now possible to make a chromeless XBlock, point a tab to it, and
make it point back to that tab.
Next steps down that path would be:
* Fix up how tabs are handled. The current version is a hack.
* Create appropriate XBlocks for courseware, tabbed navigation,
etc. to reach feature parity
* Invert/rejigger the XML format.
This change adds three new configuration variables to third_party_auth's LinkedIn provider:
* SOCIAL_AUTH_LINKEDIN_OAUTH2_SCOPE,
* SOCIAL_AUTH_LINKEDIN_OAUTH2_FIELD_SELECTORS,
* SOCIAL_AUTH_LINKEDIN_OAUTH2_EXTRA_DATA
Being able to configure these additional settings is useful if you want
the LinkedIn provider to pre-populate the email field when a new user
registers via the linkedin provider.
The Google provider prepoulates the email field by default, but if you
want LinkedIn to do the same, these two settings should be set to:
SOCIAL_AUTH_LINKEDIN_OAUTH2_SCOPE = ['r_basicprofile', 'r_emailaddress']
SOCIAL_AUTH_LINKEDIN_OAUTH2_FIELD_SELECTORS = ['email-address']
For more info see:
http://psa.matiasaguirre.net/docs/backends/linkedin.html
Declare variables locally
- The `allSections` variable was leaking into the global scope, due to a
typo in the declaration.
- `dataProcessed` can be declared more narrowly within the callback.
Clean up fixtures automatically between tests
- Nesting test fixture markup within a DIV allows Jasmine to
automatically restore the fixture to a clean state between each test
run.
Fix id attribute collision typo
- This looks like a copy/pasta gone wrong; the two test INPUT elements
were both declared with the same id, `input_1`.
Remove trailing whitespace
The behavior previously tested here was to check that if a JSInput
element was marked as not processed, re-walking the DOM *should* have
reinitialized it. Unfortunately, this behavior is not supported by the
underlying JSChannel library. In fact, if JSChannel detects an existing
channel with the same origin and scope, it throws an uncaught exception,
leaving the DOM in a "broken" state.
JSInput will prevent duplicates from being added, as long as we don't
manually update the `data-processed` attribute. This behavior is already
being tested.
