diff --git a/ckan/public/base/less/layout.less b/ckan/public/base/less/layout.less index 9ae4d86796d..f5fefffe2ab 100644 --- a/ckan/public/base/less/layout.less +++ b/ckan/public/base/less/layout.less @@ -109,6 +109,7 @@ margin: 0 0 5px 0; font-size: 18px; line-height: 1.3; + .break-word(); } .info { margin-top: 15px; diff --git a/ckan/public/base/less/media.less b/ckan/public/base/less/media.less index f18c49d0e91..ca95fbf7357 100644 --- a/ckan/public/base/less/media.less +++ b/ckan/public/base/less/media.less @@ -90,6 +90,7 @@ font-size: 18px; line-height: 1.3; margin: 5px 0; + .break-word(); } // Overlay diff --git a/ckan/public/base/less/mixins.less b/ckan/public/base/less/mixins.less index a8bbbf9c0fc..43bfb2c408c 100644 --- a/ckan/public/base/less/mixins.less +++ b/ckan/public/base/less/mixins.less @@ -1,3 +1,16 @@ +.break-word { + -ms-word-break: break-all; + word-break: break-all; + + /* Non standard for webkit */ + word-break: break-word; + + -webkit-hyphens: auto; + -moz-hyphens: auto; + -ms-hyphens: auto; + hyphens: auto; +} + .transform (@func) { -webkit-transform: @arguments; -moz-transform: @arguments; diff --git a/doc/contributing/pull-requests.rst b/doc/contributing/pull-requests.rst index 98b05c9f4dd..6909657b5c3 100644 --- a/doc/contributing/pull-requests.rst +++ b/doc/contributing/pull-requests.rst @@ -64,7 +64,7 @@ This section will walk you through the steps for making a pull request. - Your branch should contain new or changed tests for any new or changed code, and all the CKAN tests should pass on your branch, see - `Testing CKAN `_. + :doc:`test`. - Your branch should contain new or updated documentation for any new or updated code, see :doc:`documentation`. diff --git a/doc/contributing/test.rst b/doc/contributing/test.rst index f9d2f6bc805..e0316e60968 100644 --- a/doc/contributing/test.rst +++ b/doc/contributing/test.rst @@ -71,8 +71,6 @@ option:: nosetests --ckan --reset-db --with-pylons=test-core.ini ckan -If you are have the ``ckan-migration`` option on the tests will reset the -reset the database before the test run. .. _migrationtesting: @@ -84,7 +82,7 @@ Migration testing If you're a CKAN developer or extension developer and your new code requires a change to CKAN's model, you'll need to write a migration script. To ensure that the migration script itself gets tested, you should run the tests with -they ``--ckan-migration`` option, for example:: +the ``--ckan-migration`` option, for example:: nosetests --ckan --ckan-migration --with-pylons=test-core.ini ckan ckanext