Code Monkey home page Code Monkey logo

Comments (10)

anthonyjb avatar anthonyjb commented on September 28, 2024

Hi @alexandrubau, You can add new content to any area you've marked up as editable in your template, are you looking at how you might create a new page? Or are you thinking about how you might add a new editable region to a page?

If you referring to adding new content within an existing editable area then: To add a new paragrapth you can just hit the return key when an existing text element is selected (pressing enter in the middle of the text will split it so if you want it to be new position the caret at the start or end of the paragraph).

If you want to add a heading then create a new paragraph as above and use the (H)eading tool in the floating toolbox to convert the paragraph to a heading.

from contenttools.

alexandrubau avatar alexandrubau commented on September 28, 2024

Thank you very much @anthonyjb for your help.

I was referring to "If you referring to adding new content within an existing editable area".

I have noticed that holding the shift key doesn't show the pulsating border. I've tried with the left shift, with the right shift, and nothing. I'm using Windows.

Thanks

from contenttools.

anthonyjb avatar anthonyjb commented on September 28, 2024

@alexandrubau could you tell me what browser and version you're using?

from contenttools.

alexandrubau avatar alexandrubau commented on September 28, 2024

I am using Google Chrome Version 45.0.2454.101 m
How many seconds should I keep the shift key pressed ? I've hold it for about 10 seconds for each of the shift keys.

from contenttools.

ahallicks avatar ahallicks commented on September 28, 2024

+1 for this, I'm not seeing the pulse for editable regions either in Windows 10 Chrome Version 45.0.2454.101 m

from contenttools.

anthonyjb avatar anthonyjb commented on September 28, 2024

The time required to trigger the pulse is set using the ContentTools.HIGHLIGHT_HOLD_DURATION option, it defaults to 2 seconds.

I'm using Version 45.0.2454.85 Ubuntu 14.04 (64-bit) and it's working on the demo page of the site (for me). Are you both seeing the issue on the demo page? Can you let me know what OS you're using in case it's an issue with the key events? @ahallicks @alexandrubau

Thanks in advance 👍

from contenttools.

anthonyjb avatar anthonyjb commented on September 28, 2024

So...

Chrome

  • Version 45.0.2454.99 m on Windows - Not to working.
  • Version 45.0.2454.101 m on Windows - Not working.
  • Version 45.0.2454.101 (64-bit) on Ubuntu - Working.
  • Version 45.0.2454.99 on OSX - Working.
  • Version 45.0.2454.85 on Ubuntu - Working.
  • Version 46.0.2490.42 beta-m (64-bit) on Windows - Working.

Firefox

  • Version 40.0.3 on Windows - Not working.
  • Version 41 on Ubuntu - Working.

Reported to me so far. Looking like an issue specific to windows.

from contenttools.

ahallicks avatar ahallicks commented on September 28, 2024

Yeah, Chrome and Firefox don't work for me on Windows 10. However, the function that does the highlighting is being called. I added a console log in the script on my test site and it logged but the classes that do the highlighting don't get added.

from contenttools.

anthonyjb avatar anthonyjb commented on September 28, 2024

@ahallicks thanks that's really helpful - I don't have a windows box here but that gives me a starting point to look at.

from contenttools.

anthonyjb avatar anthonyjb commented on September 28, 2024

So I finally got a chance to use a few Windows machines today to try to track this bug down, I'd used browserstack to try initially but couldn't reproduce the bug on any version of windows, but today I managed to and after a few console.log statements here's what I found:

Some of the Windows machines (all Windows 8.1 but it's possible this is happening on eaelier/later version too) fire repeated key up/down events when you hold the shift key down, so because there's a time delay that checks to see if the key is being held down the timeout triggering the highlight action is cancelled because of the repeated key up/down event - so it never gets called.

It looks like FF has an event property to detect this (KeyboardEvent.repeat) but I'm not sure about other browsers yet so I'll experiment a bit more and if I can find a clean solution).

I suspect this may well be occurring on other OSs and browsers.

from contenttools.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.