profile
viewpoint
Julian Kühnel julmot @CandoImage localhost:4200 https://www.juliankuehnel.com const bio = 'I ❤ Open Source 💻';

julmot/mark.js 1774

JavaScript keyword highlighting. Mark text with with options that fit every application. Also available as jQuery plugin.

darcyclarke/Detect.js 589

:mag: Library to detect browser, os and device based on the UserAgent String

julmot/datatables.mark.js 34

A DataTables plugin for mark.js to highlight search terms in tables

julmot/news-feed-for-github 23

Chrome and Firefox extension to receive GitHub news feed notifications

julmot/nw.js-examples 8

NW.js features demonstrated in a simple project

julmot/form-components 5

Custom Form Components. Without Any Framework. Accessible.

julmot/wabp 2

*UNMAINTAINED* Kickstarter web app boilerplate with grunt builds for development and production including local server, livereload, Compass/SCSS, sprite generation, html minification, zip generation and deployment tasks. Contains RequireJS dependency management and optionally AngularJS.

julmot/flying-focus 1

UI concept

julmot/git-branch-deploy 1

A Node.js tool to deploy build artifacts to a GitHub branch using a Git commit.

julmot/angular-localize-error 0

Reproducable error for issue https://github.com/angular/angular/issues/35226

fork julmot/ng-in-viewport

Allows us to check if an element is within the browsers visual viewport

https://k3nsei.gitbook.io/ng-in-viewport/

fork in 9 days

issue commentk3nsei/ng-in-viewport

Update angular monorepo to version 10.1.0

I hope I'm not missing something but as it seems there's no documentation of inViewportOptions. Would be great to add it in this regard too.

k3nsei

comment created time in 9 days

startedk3nsei/ng-in-viewport

started time in 9 days

issue commentapollographql/apollo-feature-requests

Feature idea: Abort pending requests

I also really need this to have the possibility to mark several filters as checked and only take continue with the latest requrest but cancel any earlier requests. While I was able to .unsubscribe() on a watchQuery to make sure my code isn't execute redundantly (see e.g. https://github.com/apollographql/apollo-client/issues/4150#issuecomment-500127694) the requests will still be handled by the browser. What I really need is a way to cancel the request on a network layer side.

klis87

comment created time in 11 days

startedmdn/dom-examples

started time in 11 days

created tagjulmot/form-components

tagv1.1.2

Custom Form Components. Without Any Framework. Accessible.

created time in 11 days

release julmot/form-components

v1.1.2

dist.zip 0.26MB

released time in 11 days

push eventjulmot/form-components

Julian Kühnel

commit sha fee39dfd4347f71aebaf1b80351dfe2b9ee7aba9

Update patch release version

view details

push time in 11 days

push eventjulmot/form-components

Julian Kühnel

commit sha 769d629038b8edb0f1cc7510a081c37dc14a31b0

Don't handle interaction when disabled in checkbox component

view details

push time in 11 days

startedclbond/form-example

started time in 12 days

PR opened DataTables/Plugins

Update datatables.mark.js to v2.0.2

Hi @DataTables, Even though this release doesn't include a change from a code perspective - rather only a fix of the package.json, I've still updated the plugin here to ensure there is no confuseness e.g. "why isn't it up to date?". Cheers 🍾

+9 -9

0 comment

4 changed files

pr created time in 13 days

push eventjulmot/Plugins

Julian Kühnel

commit sha bb726ed5915682d348dbb25e0113dd3ee131da03

Update datatables.mark.js to v2.0.2

view details

push time in 13 days

fork julmot/Plugins

Plug-ins for DataTables

fork in 13 days

created tagjulmot/datatables.mark.js

tagv2.0.2

A DataTables plugin for mark.js to highlight search terms in tables

created time in 13 days

push eventjulmot/datatables.mark.js

Julian Kühnel

commit sha 3372ba39f271d10651b9b208bc11135f7532ca67

Release preparations v2.0.2

view details

push time in 13 days

PR closed julmot/datatables.mark.js

Update karma to the latest version 🚀 greenkeeper

The devDependency karma was updated from 3.1.4 to 4.0.1.

This version is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.


<details> <summary>Release Notes for v4.0.1</summary>

<h3>Bug Fixes</h3> <ul> <li><strong>browser:</strong> allow updating total specs count (<a href="https://urls.greenkeeper.io/karma-runner/karma/issues/3264" data-hovercard-type="pull_request" data-hovercard-url="/karma-runner/karma/pull/3264/hovercard">#3264</a>) (<a href="https://urls.greenkeeper.io/karma-runner/karma/commit/d5df723">d5df723</a>)</li> <li>remove vulnerable dependency combine-lists (<a href="https://urls.greenkeeper.io/karma-runner/karma/issues/3273" data-hovercard-type="pull_request" data-hovercard-url="/karma-runner/karma/pull/3273/hovercard">#3273</a>) (<a href="https://urls.greenkeeper.io/karma-runner/karma/commit/c43f584">c43f584</a>), closes <a href="https://urls.greenkeeper.io/karma-runner/karma/issues/3265" data-hovercard-type="issue" data-hovercard-url="/karma-runner/karma/issues/3265/hovercard">#3265</a></li> <li>remove vulnerable dependency expand-braces (<a href="https://urls.greenkeeper.io/karma-runner/karma/issues/3270" data-hovercard-type="pull_request" data-hovercard-url="/karma-runner/karma/pull/3270/hovercard">#3270</a>) (<a href="https://urls.greenkeeper.io/karma-runner/karma/commit/4ec4f6f">4ec4f6f</a>), closes <a href="https://urls.greenkeeper.io/karma-runner/karma/issues/3268" data-hovercard-type="issue" data-hovercard-url="/karma-runner/karma/issues/3268/hovercard">#3268</a> <a href="https://urls.greenkeeper.io/karma-runner/karma/issues/3269" data-hovercard-type="issue" data-hovercard-url="/karma-runner/karma/issues/3269/hovercard">#3269</a></li> <li><strong>filelist:</strong> correct logger name. (<a href="https://urls.greenkeeper.io/karma-runner/karma/issues/3262" data-hovercard-type="pull_request" data-hovercard-url="/karma-runner/karma/pull/3262/hovercard">#3262</a>) (<a href="https://urls.greenkeeper.io/karma-runner/karma/commit/375bb5e">375bb5e</a>)</li> <li><strong>launcher:</strong> Debug Child Processes exit signal (<a href="https://urls.greenkeeper.io/karma-runner/karma/issues/3259" data-hovercard-type="pull_request" data-hovercard-url="/karma-runner/karma/pull/3259/hovercard">#3259</a>) (<a href="https://urls.greenkeeper.io/karma-runner/karma/commit/c277a6b">c277a6b</a>)</li> </ul> </details>

<details> <summary>Commits</summary> <p>The new version differs by 20 commits.</p> <ul> <li><a href="https://urls.greenkeeper.io/karma-runner/karma/commit/c7ebf0bd7343d9e7afe683005c38ba1cb4a7752b"><code>c7ebf0b</code></a> <code>chore: release v4.0.1</code></li> <li><a href="https://urls.greenkeeper.io/karma-runner/karma/commit/c190c4a60a708be4115f9726da964e2d23116269"><code>c190c4a</code></a> <code>chore: update contributors</code></li> <li><a href="https://urls.greenkeeper.io/karma-runner/karma/commit/375bb5e37c34535e222e019d0b11454f5a2b1593"><code>375bb5e</code></a> <code>fix(filelist): correct logger name. (#3262)</code></li> <li><a href="https://urls.greenkeeper.io/karma-runner/karma/commit/c43f58427227e6a7fbaa95420a72ca9018839b87"><code>c43f584</code></a> <code>fix: remove vulnerable dependency combine-lists (#3273)</code></li> <li><a href="https://urls.greenkeeper.io/karma-runner/karma/commit/4ec4f6f26b175e3f759dfae9c1ba6a41654185da"><code>4ec4f6f</code></a> <code>fix: remove vulnerable dependency expand-braces (#3270)</code></li> <li><a href="https://urls.greenkeeper.io/karma-runner/karma/commit/d5df723f97d1b48133416109276feebb0c6fa82d"><code>d5df723</code></a> <code>fix(browser): allow updating total specs count (#3264)</code></li> <li><a href="https://urls.greenkeeper.io/karma-runner/karma/commit/c277a6bd130531702e2529f0410aa441328f187e"><code>c277a6b</code></a> <code>fix(launcher): Debug Child Processes exit signal (#3259)</code></li> <li><a href="https://urls.greenkeeper.io/karma-runner/karma/commit/bd95d89044ecd68c088d56797fe87cc170a7991f"><code>bd95d89</code></a> <code>chore: upgrade log4js to v4.0.0 (#3257)</code></li> <li><a href="https://urls.greenkeeper.io/karma-runner/karma/commit/5a47718e5c621a7afc549353e9bef60ff2d2dc0d"><code>5a47718</code></a> <code>chore: release v4.0.0</code></li> <li><a href="https://urls.greenkeeper.io/karma-runner/karma/commit/56cc239388b1df8b92f68216fb408adc287603f9"><code>56cc239</code></a> <code>chore: update contributors</code></li> <li><a href="https://urls.greenkeeper.io/karma-runner/karma/commit/d59cf35564d1b4e0e6a24ef52dd8406a5616eca2"><code>d59cf35</code></a> <code>refactor(watcher): Make watcher injectable to support 3rd-party watchers (#3254)</code></li> <li><a href="https://urls.greenkeeper.io/karma-runner/karma/commit/988b9010e9127e18f989a2a2fd7c32a069f1d7f2"><code>988b901</code></a> <code>chore(license): Update copyright notice to 2019 [ci skip] (#3250)</code></li> <li><a href="https://urls.greenkeeper.io/karma-runner/karma/commit/571191cfbe41010c6fa4283bd7d8447d5fcbb4ba"><code>571191c</code></a> <code>fix(client): fix issue with loaded on safari 10 (#3252)</code></li> <li><a href="https://urls.greenkeeper.io/karma-runner/karma/commit/376142e282d09ae827038969414498f586ab00cd"><code>376142e</code></a> <code>refactor(fileList): refactor with async/await (#3247)</code></li> <li><a href="https://urls.greenkeeper.io/karma-runner/karma/commit/acdd2dc2ccdd054f0845455d762919f5f2dff561"><code>acdd2dc</code></a> <code>refactor(server): refactor start method to use async/await (#3245)</code></li> </ul> <p>There are 20 commits in total.</p> <p>See the <a href="https://urls.greenkeeper.io/karma-runner/karma/compare/b8b8618b08acf14e3e4d435904029fe7a18134f3...c7ebf0bd7343d9e7afe683005c38ba1cb4a7752b">full diff</a></p> </details>

<details> <summary>FAQ and help</summary>

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper. </details>


Your Greenkeeper bot :palm_tree:

+1 -1

1 comment

1 changed file

greenkeeper[bot]

pr closed time in 13 days

startedstritti/log4js

started time in 19 days

startedlog4js-node/log4js-node

started time in 19 days

startedmfranzke/loading-attribute-polyfill

started time in 19 days

startedphw198/OutlookGoogleCalendarSync

started time in 20 days

issue commentjust-jeb/angular-builders

Custom webpack @ extract-i18n | Angular 10.1

Unfortunately I can't anymore. After this has been idle from the ng team for so long, I've refactored my build process to avoid custom webpack configurations.

julmot

comment created time in 20 days

issue closedjulmot/mark.js

Multiple keyword styling options in FireFox Reader View mode

Currently, it is indeed possible to use multiple highlighting colors for different keywords.

However, this is not possible in FireFox Reader View mode, as all highlighted keywords are shown using one single color, and that's yellow. I tried applying various CSS styling options (color, background, text-decoration), but none of them seem to work. I did that through the 'className' mark.js option.

So, I was wondering if there's any way to use different marking styles in FireFox Reader View mode, and if not, then I'd like to submit this idea for future development consideration.

Thank you,

Alex

closed time in 24 days

Alex839

issue commentjulmot/mark.js

Multiple keyword styling options in FireFox Reader View mode

I have no experience with Reader View Mode, but if there are any styling limitations this is not related to mark.js but to all elements on the page. I guess this is the purpose of it - to remove all stylings and instead visualize only the text in a readable way. mark.js simple generates HTML elements with a specific class. You can test stylings with any other element too.

Alex839

comment created time in 24 days

issue closedjulmot/mark.js

Instruct mark.js not to highlight a previously highlighted keyword

> Is your feature request related to a problem? Please describe.

mark.js highlights keywords that have already been highlighted before.

> Describe the solution you'd like

I believe it would be best to let the user decide how mark.js should behave when it is about to highlight a previously highlighted keyword.

To give you an example, here is this short sentence:

'These flowers are very beautiful!'

Below you will find a script where I set up mark.js to highlight keyword 'very beautiful' in green, and keyword 'beautiful' in blue. Obviously, what I would like to see, is a sentence where words 'very beautiful' are both colored in green. Instead, what I get is word 'very' highlighted in green, and word 'beautiful' in blue.

You can run the code here:

https://jsfiddle.net/Alex100/1sapmq3r

Like I said, I think it would be best to set up an option where you can instruct mark.js not to highlight a keyword if this is part of another previously highlighted keyword.

Switching the order in which the 'markRegExp' function is called is not a solution, at least not for me. I have hundreds of keywords, and it would be nearly impossible to keep track of how they all interact with each other.

In the end, I would like to take this opportunity to thank you for this wonderful script!

Thank you!

Alex

closed time in 24 days

Alex839

issue commentjulmot/mark.js

Instruct mark.js not to highlight a previously highlighted keyword

Since there's a solution here (thanks for that!) I'm going to close this issue.

Alex839

comment created time in 24 days

issue closedCandoImage/redmine-slack-bot

Install process

Hi,

Could you please explain how to install your bot please ?

Thank's !

closed time in 24 days

matnoublanche

issue commentCandoImage/redmine-slack-bot

Install process

You'll have to install Node.js and then run $ npm install && npm run dev in the root folder of the project. I'd recommend to host it somewhere. Please note that this project 3.5 years old and hasn't been used since then, so I don't know if it still works.

matnoublanche

comment created time in 24 days

issue openedpimcore/data-hub

Consistent IDs

Create an object type "Product", then you'll get at least two methods automatically:

  1. getProduct
  2. getProductListing

This is fine. However, getProduct requires an Integer as the ID, whereas getProductListing only accepts a string with comma separated values instead of an array.

Anmerkung 2020-08-13 134747 Anmerkung 2020-08-13 134847

Both, from my understanding, should rather support the actual response type of ID, which is:

Anmerkung 2020-08-13 134945

Also getProductListing should not have comma separeted IDs but an array of IDs.

created time in a month

issue commentjulmot/mark.js

Instruct mark.js not to highlight a previously highlighted keyword

Hi, have you tried the filter method or the exclude option?

Alex839

comment created time in a month

startedmengshukeji/Luckysheet

started time in 2 months

issue commentHaehnchen/idea-localization-plugin

Not compatible with Intellij IDEA 2020.2

Seems to be fixed with https://github.com/Haehnchen/idea-localization-plugin/commit/c87e9d6c78421785e3f69d96a8acba04a1fcb029

Thunderforge

comment created time in 2 months

startedHaehnchen/idea-php-symfony2-plugin

started time in 2 months

startedapollographql/apollo-cache-persist

started time in 2 months

issue commentHaehnchen/idea-localization-plugin

Not compatible with Intellij IDEA 2020.2

Same issue here.

Thunderforge

comment created time in 2 months

startedHaehnchen/idea-localization-plugin

started time in 2 months

startedl-lin/angular-datatables

started time in 2 months

startedRequarks/wiki

started time in 2 months

startedsindresorhus/terminal-image

started time in 2 months

startedYannickDot/console.image

started time in 2 months

startedadriancooney/console.image

started time in 2 months

startedescusado/console.meme

started time in 2 months

created tagjulmot/form-components

tagv1.1.1

Custom Form Components. Without Any Framework. Accessible.

created time in 2 months

release julmot/form-components

v1.1.1

dist.zip 0.15MB

released time in 2 months

push eventjulmot/form-components

Julian Kühnel

commit sha 249e43eb00719fa8856879e94e33c22583320c82

Fix select component for being used decoupled Also part of this commit: * Align with @fractal/mendelbrot template change * Update dependencies

view details

push time in 2 months

issue commentatomiks/tippyjs

When using "mouseenter click", then "hideAll" doesn't work correctly

@atomiks When it'll be released?

fyi: I've just noticed that the behavior I want to have here is already the default on mobile (touch) devices it seems.

julmot

comment created time in 2 months

issue commentpimcore/data-hub

Documents @ DataHub

I've just re-checked the progress on this topic, seems like there's now basic support to read documents decoupled. But seems like support for bricks is missing and also the part of integrating decoupled apps into the WYSIWYG editor of Pimcore seems to be open.

julmot

comment created time in 2 months

issue commentpimcore/data-hub

Update- & Delete-Mutations (and references in relationships): allow path as an alternative to id for identifying object

Would also be cool for documents, to be able to read documents based on path, when you don't know the ID (stage specific).

Iblis

comment created time in 2 months

issue commentpimcore/pimcore

GraphQl (DataHub) Elasticseach(advenced-object-search) integration

Thanks for re-opening. I would like to share our use cases:

  • We want to integrate an instant search dropdown with about 10 fuzzy search results
  • We want to integrate a product listing page with filters

We've already opened a PR in data-hub for a part of it.

However, the main question is how DataHub should be integrated with Elasticsearch to get really fast search results. Either by connecting Elasticsearch from Pimcore or by directly requesting the GraphQl query at Elasticsearch.

not4fame

comment created time in 2 months

issue commentpimcore/pimcore

GraphQl (DataHub) Elasticseach(advenced-object-search) integration

Also need this, imho not really an issue to be discussed in a forum, rather a feature request for an integration directly in GraphQl (DataHub).

not4fame

comment created time in 2 months

startedrough-stuff/rough-notation

started time in 2 months

startedKikobeats/unavatar

started time in 2 months

issue commentnolimits4web/swiper

Swiper v6 CSS not generated with Webpack in PROD builds

@nolimits4web

Would it be possible to specify these CSS files to have side-effects, like (?): webpack/webpack#6571 (comment)

julmot

comment created time in 2 months

issue commentatomiks/tippyjs

When using "mouseenter click", then "hideAll" doesn't work correctly

I can't confirm it's working. My example and the steps to reproduce will still show the issue. Since this example is using @6.x.x version it automatically uses the patch version v6.2.5.

Example: https://jsfiddle.net/oxpqLz9u/ Steps:

  1. Click on the first tooltip
  2. Hover over the second tooltip
  3. Click on the first tooltip again

=> After the hover of the second tooltip the first tooltip should be closed. This works. But then, when clicking on the first tooltip again instead of re-opening it, it closes it. Usually it should stay open for either another click or when another instance is hovered.

julmot

comment created time in 2 months

issue commentangular/angular

routerLink directive always makes element focusable

My use case: I always have accessibility in mind and for me the behavior of routerLink seems to be correct. But, I need to break accessibility intentionally to have a specific tabbing experience for speed users of a B2B eCommerce system. They want to order very fast and so only buy buttons should be focusable in this specific context. Thus, I need to have the ability to disable this behavior of routerLink.

akloeber

comment created time in 3 months

issue commentscttcper/ngx-toastr

How to get toast Id?

const toast = this.toastr.success(...);
console.log(toast.toastId);
aks7665

comment created time in 3 months

issue commentscttcper/ngx-toastr

Feature Request: Pass data to custom component

Example from my app:

  private createToast(
    name: string | null,
    image: IImage | null,
    type: 'success' | 'error',
  ): void {
    const toast = this.toastr.success(null, name, {
      toastComponent: AddToCartToastComponent,
      closeButton: true,
      tapToDismiss: false,
      timeOut: 5000,
      extendedTimeOut: 5000,
    });
    toast.toastRef.componentInstance.status = type;
    if (image) {
      toast.toastRef.componentInstance.image = image;
    }
  }
shyamal890

comment created time in 3 months

startedscttcper/ngx-toastr

started time in 3 months

startedneedim/noty

started time in 3 months

startedCodeSeven/toastr

started time in 3 months

issue commentnolimits4web/swiper

Swiper v6 CSS not generated with Webpack in PROD builds

Since the post you've mentioned is open for over two years it's unlikely that it'll be solved soo. So, what should Swiper users do when they have a Webpack project, which for me, is like industry standard for non-libraries?

Would it be possible to specify these CSS files to have side-effects, like: https://github.com/webpack/webpack/issues/6571#issuecomment-368405434

julmot

comment created time in 3 months

issue commentnolimits4web/swiper

Swiper v6 CSS not generated with Webpack in PROD builds

https://github.com/nolimits4web/swiper/blob/77d72e411ef91b7580eb8fb96f05f0e43a0a6b90/build/bundle/package.json#L8

julmot

comment created time in 3 months

issue commentnolimits4web/swiper

Swiper v6 CSS not generated with Webpack in PROD builds

After further investigation I can now confirm the reason is "sideEffects": false in the package.json of the npm package. What was the background of this respectively why was it added? I compared this to the v5 Swiper npm package and it wasn't present there, so this is the reason for the issue here.

julmot

comment created time in 3 months

startedtristen/tablesort

started time in 3 months

issue openednolimits4web/swiper

Swiper v6 CSS not generated with Webpack in PROD builds

<!--

Do you want to ask a question? Are you looking for support? Stack Overflow (http://stackoverflow.com/questions/tagged/swiper) is the best place for getting support

-->

This is a (multiple allowed):

  • [x] bug

  • [ ] enhancement

  • [ ] feature-discussion (RFC)

  • Swiper Version: v6.0.1

  • Platform/Target and Browser Versions: Windows 10

What you did

I've upgraded from v5.4.5 to v6.0.1.

Expected Behavior

I changed the imports from

import Swiper from 'swiper';
import 'swiper/css/swiper.css';

to

import Swiper from 'swiper/bundle';
import 'swiper/swiper-bundle.css';

and expected it to work, since I have none of the breaking changes implemented, mentioned in the CHANGELOG.

Actual Behavior

The CSS contents is missing in my webpack build since the upgrade, without changed webpack configuration. For example this is missing:

.swiper-slide {
  flex-shrink: 0;
  width: 100%;
  height: 100%;
  position: relative;
  transition-property: transform; }

For compiling SASS/SCSS/CSS my Webpack configuration looks like:

      { // sass and postcss at the end
        test: /\.(scss|css)$/,
        use: [
          miniCssExtractPlugin.loader,
          {
            loader: 'css-loader'
          }, {
            loader: 'postcss-loader',
            options: {
              config: {
                path: path.join(__dirname, './postcss.config.js'),
              }
            }
          }, {
            loader: 'sass-loader',
            options: {
              sassOptions: {
                includePaths: [
                  'node_modules'
                ]
              }
            }
          }]
      }

Since the change is quite huge it's nearly impossible for me to find the related thing to this. However, what I could imagin is that since the entire bundle architecture was refactored, this may be related to Webpack's tree shaking algorithm or the sideEffects property in package.json.

What could be the issue here?

Maybe related to https://github.com/nolimits4web/swiper/issues/3671

created time in 3 months

startedtypescript-eslint/tslint-to-eslint-config

started time in 3 months

startedangular-eslint/angular-eslint

started time in 3 months

startedtypescript-eslint/typescript-eslint

started time in 3 months

issue closedjulmot/mark.js

pass the search result to scrollIntoView

I am keen to pass the search result (if find any) to the scrollIntoView function in jQuery.

I use the code below for the search:

   $input.on("input", function () {
            var searchVal = this.value;
            $content.unmark({
                done: function () {
                    $content.mark(searchVal, {
                        "wildcards": "disabled",
                        "accuracy": "exactly",
                        "iframes": true,
                        "ignoreJoiners": false,
                        "acrossElements": true,
                        "separateWordSearch": false,
                        done: function () {
                            $results = $content.find("mark");
                            currentIndex = 0;
                            jumpTo();
                        }
                    });
                }
            });
        });

here the function jumpTo() is defined as

   function jumpTo() {
            if ($results.length) {
                var position,
                    $current = $results.eq(currentIndex);
                $results.removeClass(currentClass);
                if ($current.length) {
                    $results.scrollIntoView({
                        block: 'center',
                        inline: 'center'
                    });
                }
            }
        }

but it does not work and instead gives me the error below: 19:1380 Uncaught TypeError: $results.scrollIntoView is not a function

I further require the search scrolls to elements one by one if there are more than one results.

Please can you help?

Than you very much for your time.

closed time in 3 months

omidMolaverdi

issue closedjulmot/mark.js

use with tinymce

Hi i am using markjs with angular 7. How can i mark text inside tinymce when i have a multiple editors? this is my code: var options = { accuracy: "exactly" }; var context = document.querySelector(".writting-section"); var instance = new Mark(context); instance.mark(textArray,options); }, 1000); the writing-section is the wrapper of all the editors. when i mark text outside the editors it works. i will appreciate for an answer?

Thanks

closed time in 3 months

guypeled1

push eventjulmot/flying-focus

Julian Kühnel

commit sha 5eabc79834a8845a2f7939bde9a579763b15fed1

On mousedown anywhere, close flying-focus

view details

push time in 3 months

push eventCandoImage/flying-focus

Julian Kühnel

commit sha b020d19768a87130f5b9584131b55a0f15de91aa

Create package.json

view details

push time in 3 months

issue commentatomiks/tippyjs

When using "mouseenter click", then "hideAll" doesn't work correctly

Since it should toggle on click, I would not like to set hideOnClick: false. Would you mind to elaborate what you mean with this?

or when it's true, the isVisibleFromClick/shouldScheduleClickHide variables need to be tweaked for this case

julmot

comment created time in 3 months

issue openedatomiks/tippyjs

When using "mouseenter click", then "hideAll" doesn't work correctly

Bug description

I want tippy to appear on click and disappear on click again. Also I want it to work on hover.

This works with the trigger mouseenter click without any customizations. Now, what I need additionally is to close all existing tippy instances that were shown on click when hovering another tippy. So, let's say you're showing a tippy instance by clicking on it, then hovering over another tippy instance. Then two instances will be shown at the same time. This is what I'd like to avoid.

Based on the amazin documentation I tried my luck with:

[...document.querySelectorAll('.test')].forEach(toggle => {
  tippy(toggle, {
    content: toggle.getAttribute('data-content'),
    trigger: 'mouseenter click',
    onShow: instance => {
      tippy.hideAll({
        exclude: instance
      })
    }
  })
});

While this works for the first time, it doesn't work for all others.

Reproduction

Example: https://jsfiddle.net/oxpqLz9u/

Steps:

  1. Click on the first tooltip
  2. Hover over the second tooltip
  3. Click on the first tooltip again

=> After the hover of the second tooltip the first tooltip should be closed. This works. But then, when clicking on the first tooltip again instead of re-opening it, it closes it. Usually it should stay open for either another click or when another instance is hovered.

created time in 3 months

issue openedyowainwright/stickybits

Use IntersectionObserver

I'd suggest using IntersectionObserver when possible as I assume this is more performant:

https://developers.google.com/web/updates/2017/09/sticky-headers

created time in 3 months

issue commentpimcore/data-hub

Create Data Object Variant

Have you seen this?

https://github.com/pimcore/data-hub/blob/master/doc/graphl/Mutations.md#create-object

kobs123

comment created time in 3 months

issue commentjulmot/mark.js

use with tinymce

Hi,

Thanks for submitting.

Please read the contribution guidelines and provide the required information named there.

guypeled1

comment created time in 3 months

startedd3/d3

started time in 3 months

issue commentmartinroob/ngx-i18nsupport

Package "@ngx-i18nsupport/tooling" has an incompatible peer dependency to "@angular/core" /"@angular/common" when updating to angular 10.0.0

It seems to be compatible with v10, so I think it's only necessary to perform the update...

laurapebe

comment created time in 3 months

startedstefanjudis/tiny-helpers

started time in 3 months

issue openedapollographql/apollo-feature-requests

Avoid importing non ES6 dependencies

Since v10 Angular is showing a warning for graphql-tag since it's a CommonJS import that should now be replaced with ES6 code. The same applies for apollo's dependencies itself, for example the "zen-observable" dependency is a CommonJS dependency used by apollo-client and apollo-link according to npm ls:

+-- apollo-client@2.6.10
| `-- zen-observable@0.8.15
`-- apollo-link@1.2.14
  `-- zen-observable-ts@0.8.21
    `-- zen-observable@0.8.15  deduped

This will show a warning in the console and in the browser by Angular:

WARNING in P:\cando-cx-frontend\app\node_modules\zen-observable-ts\lib\bundle.esm.js depends on zen-observable. CommonJS or AMD dependencies can cause opt
imization bailouts.

To avoid this, apollo should avoid using CommonJS dependencies.

Related:

https://github.com/apollographql/graphql-tag/issues/303

created time in 3 months

issue openedapollographql/graphql-tag

Implement ES6 export file

Angular worked on the build process in v10 and removed support for already transpiled code to ES5 for Angular Libraries. Also they now show a warning for every dependency that is imported in ES5.

More information: https://angular.io/guide/build#configuring-commonjs-dependencies

Example warning:

WARNING in P:\XXX\XXX.js depends on graphql-tag. CommonJS or AMD
 dependencies can cause optimization bailouts.

To avoid this we'd need an ES6 file in "main" property of package.json or at least a file in the lib folder in ES6 that can be imported directly. This should be the feature request of this issue.

created time in 3 months

more