usfm-editor
Version:
A WYSIWYG editor component for USFM
39 lines (33 loc) • 2.93 kB
JavaScript
;
Object.defineProperty(exports, "__esModule", {
value: true
});
exports.SelectionSeparator = void 0;
var React = _interopRequireWildcard(require("react"));
function _getRequireWildcardCache(nodeInterop) { if (typeof WeakMap !== "function") return null; var cacheBabelInterop = new WeakMap(); var cacheNodeInterop = new WeakMap(); return (_getRequireWildcardCache = function (nodeInterop) { return nodeInterop ? cacheNodeInterop : cacheBabelInterop; })(nodeInterop); }
function _interopRequireWildcard(obj, nodeInterop) { if (!nodeInterop && obj && obj.__esModule) { return obj; } if (obj === null || typeof obj !== "object" && typeof obj !== "function") { return { default: obj }; } var cache = _getRequireWildcardCache(nodeInterop); if (cache && cache.has(obj)) { return cache.get(obj); } var newObj = {}; var hasPropertyDescriptor = Object.defineProperty && Object.getOwnPropertyDescriptor; for (var key in obj) { if (key !== "default" && Object.prototype.hasOwnProperty.call(obj, key)) { var desc = hasPropertyDescriptor ? Object.getOwnPropertyDescriptor(obj, key) : null; if (desc && (desc.get || desc.set)) { Object.defineProperty(newObj, key, desc); } else { newObj[key] = obj[key]; } } } newObj.default = obj; if (cache) { cache.set(obj, newObj); } return newObj; }
/**
* The user's selection cannot be expanded through this zero-width space. This partially solves the
* problem where the user double- or triple-clicks on a word, causing the selection to span through
* a non-contentEditable node (like a verse number or chapter number.) This works well when the
* SelectionSeparator is added directly after a verse/chapter number; the user's selection stays
* to the RIGHT of the number (i.e. within the desired verse). However, empirical obersvation shows that
* placing the SelectionSeparator directly before a verse/chapter number does NOT prevent the case where
* the user double/triple clicks on a word in the preceding verse, and the selection expands through the
* next verse's verse number.
*
* Furthermore, placing the SelectionSeparator at the end of a verse node or the last editable node
* within a verse (such as an inlineContainer or a paragraph) causes the visible cursor to disappear
* when the selection is at the end of that node.
*
* Therefore, it is currently only recommended to place the SelectionSeparator directly after a
* non-contentEditable node (such as a verse/chapter number). The directionality of the user's intended
* selection can be inferred from the fact that any selection through the non-contentEditable node must
* have originated to the LEFT of that node.
*/
const SelectionSeparator = () => /*#__PURE__*/React.createElement("span", {
// Zero-width space ensures that selection stays to the right of the verse number
className: "usfm-editor-no-select",
contentEditable: false
}, "\u200B");
exports.SelectionSeparator = SelectionSeparator;