Atto: Full screen

Maintained by Picture of Daniel ThiesDaniel Thies
An Atto plugin which enables full screen editing mode
2933 sites
47 fans
Current versions available: 1

This plugin adds a button to the toolbar which will expand the Atto editing window to fill the entire browser window.  All other parts of the page are hidden.


Screenshot #0
Screenshot #1


Picture of Daniel Thies
Daniel Thies (Lead maintainer)
Please login to view contributors details and/or to contact them

Comments RSS

Show comments
  • Just wondering . . .
    Wed, Jan 13, 2016, 5:51 AM
    I am getting a clash with this plugin and Flexibase. The Awesome Bar obscures the buttons on the editor.
    I have a screen snap here:
    Do you have a suggested fix?

  • Picture of Daniel Thies
    Wed, Jan 13, 2016, 6:42 AM
    Hi Derek,
    The full screen plugin hides decorations or navigation in other themes using CSS. You should be able to hide the Awesome Bar if you have the selector (right click and inspect element in browser) by adding custom CSS to the theme or by adding it to the plugin style.css file. Examples of how to do this are found in style.css.
  • Picture of Daniel Thies
    Wed, Jan 13, 2016, 7:49 AM
    .atto-fullscreen #awesomebar {
    display: none;
    visibility: hidden
    to styles.css file and clearing the theme cache will hide the awesomebar when the editor is expanded. Is that what you intend? Or is the editor suppose to adjust around the awesomebar?
  • Picture of Brian Warling
    Wed, Jan 13, 2016, 7:54 AM
    Hi -- We installed the latest version (2015122000) on our Moodle 2.7.11 site (2014051211.02). Clicking on the full screen button works -- Atto goes full screen. But clicking it again does nothing -- the screen does not go back. You're basically stuck. The only way to get out is to use the browser back button, which takes you out of Atto. I'm seeing this on our custom theme, and also on the Clean theme. We were not seeing this problem using the previous version. Please let me know if you need any more info from me on this. Thanks... Brian
  • Just wondering . . .
    Wed, Jan 13, 2016, 8:23 AM
    @Daniel, thanks, that worked.
    And that was really quick too!!

    Next question. I think I am pushing Moodle + Bootstrap and coding a bit much at the moment.
    I got this in red:
    <="" div ""=>
    in one bit of code, and I am often getting the last part of a p tag close in red.
    Is there any information on how HTML+ actually works?
    I've also been trying to cut and paste code into a text editor to see if it will help.
    Is there a way to press a button and tidy up the code again in ATTO?
    Very very much easier with HTMLPlus, but just wondering if I am missin gout on anything.

  • Picture of Daniel Thies
    Wed, Jan 13, 2016, 8:50 AM
    Hi Brian,
    Try using F12 to open the javascript console to see if there is a javascript error of some type. I do not think the upgrade should have caused that, and I have not seen it. Do you have any other editor plugins installed that may be conflicting with it?
  • Picture of Daniel Thies
    Wed, Jan 13, 2016, 9:46 AM
    I have not tried cut and paste within the HTML+ editor, but I would not be surprised if it had problems at least in some browsers. I do not think that it is what is intended for. The regular HTML plugin may be better suited for that or the Paste Special plugin. What you see with HTML+ view is actually a contenteditable div superimposed over the text area. This plugin resizes it, but the inner workings are rather complicated. Bootstrap is not really my area either.
  • Picture of Brian Warling
    Thu, Jan 14, 2016, 3:54 AM
    Hi Derek -- Thanks for your comments. I am seeing what appears to be javascript errors; e.g.:

    Uncaught TypeError: Cannot read property 'all' of null

    TypeError: null is not an object (evaluating 'host.toolbar.ancestor('.editor_atto_wrap').all')
    (anonymous function)yui_combo.php:12201
    (anonymous function)yui_combo.php:370

    I've tested this on a clear Moodle 2.7.12 instance, with only the fullscreen plugin included. I see the error here, too. I am NOT seeing the error on a new Moodle 3.0.2 server.

    Please let me know if you need any more info. Thanks very much for your help. Thanks.... Brian
  • Picture of Daniel Thies
    Thu, Jan 14, 2016, 8:32 AM
    Hi Brian,
    This looks like it will be very helpful. Thank you. I do not think I have tested 2.7 recently and the editor has had many changes since then. I should be able to reproduce it now.
  • Picture of Daniel Thies
    Fri, Jan 15, 2016, 12:56 AM
    Thanks again for reporting this, Brian. It should fixed it the new release. Please check it and let me know how it works for you.
  • cb userpic w harvey
    Thu, Oct 6, 2016, 10:19 AM
    Hi Daniel,

    Just tried installing in 3.1.2, got this error and wept because I love the plugin:


    More information about this error
    Debug info:
    Error code: installing_non_installable_component
    $a contents:
    Stack trace:

    line 67 of /admin/tool/installaddon/index.php: moodle_exception thrown

  • cb userpic w harvey
    Thu, Oct 6, 2016, 10:48 AM
    Hi again,

    Figured it out: installing from Plugins directory throws the error. I downloaded, uploaded to Install Plugins, and selected the Atto HTML Editor directory in the "More..." dropdown. It worked then.

    Thanks so much, again. smile
  • Picture of Stewart Fulton
    Mon, Feb 12, 2018, 9:56 AM
    Does the strings used in this plugin require that TinyMCE be installed as well?
    After installation the debugging code appeared: "String does not exist. Please check your definition for fullscreen:desc/editor_tinymce"
    Thank you
  • Picture of Daniel Thies
    Mon, Feb 12, 2018, 11:24 AM
    @Stewart unfortunately is does at the moment. I used the string so it would work without translation, but I did not anticipate that anyone would be removing TinyMCE anytime soon. However, it has been a while that should problably be revisited.
  • Picture of Daniel Thies
    Mon, Feb 12, 2018, 12:01 PM
    Other plugins use pluginname for the tooltip so there is not a real reason not to do that here. I updated it so it should work without TinyMCE.
1 2
Please login to post comments