not showing date calender in vuejs,
Date doesn't show UI on safari browser. where this date received a response from the service.
thus on android and windows can display the date calendar. it doesn't work on ios safari, chrome or mac. is there a best solution for this case?
not showing date calender in vuejs, Date doesn't show UI on safari browser. where this date received a response from the service. thus on android and windows can display the date calendar. it doesn't work on ios safari, chrome or mac. is there a best solution for this case?
I've researched on the same issue you have. I got my answer from this thread https://github.com/date-fns/date-fns/issues/2130 I used the parse function in date-fns.
Instead of new Date('2022-11-25') I used parse('2022-11-25', 'yyyy-MM-dd', new Date()).
Please note that 'yyyy-MM-dd' is based on the document of date-fns, I suggest you follow the examples there.
Related
We use Elastic Search throughout most of our app, and up until today, we've never had issues with testing those features via Cypress. One feature in our app is a calendar tool that populates a list with appointment dates and times. When accessing this calendar tool manually via Chrome, the list correctly populates without issue. When opening this tool during a Cypress spec, and ONLY during a Cypress spec, the results fail to load. The console spits out an error that just says "[useElasticsearch] incorrect header check" with no other information. In checking the network tab, we can confirm that the ES query is performed and returns results successfully, but the page is not updated with those results.
Note that this is NOT the result of a cy.request(), this error occurs through standard UI navigation. This issue, as I mentioned, ONLY occurs when testing via Cypress. Due to this, we are hesitant to make changes to the backend of the app, since it works perfectly fine in all other scenarios. This has been reproduced on Cypress versions 5.1.0, 6.1.0, 7.1.0, and 8.0.0. This has also been reproduced in Cypress when using the Chrome, Electron, and headless browsers.
Has anybody else encountered this issue?
I've been trying to understand why body.prependAsync() does not work only on Outlook for Mac (current UI with Microsoft365 Subscription). For all other browsers and Outlook for Mac (new UI with Microsoft365 Subscription), it is working perfectly; meaning the body of the email is being populated correctly. The API version being used is 1.7 and I can see that it's supported in this documentation.
The error that I'm receiving in the callback from body.prependAsync() is:
[2006] Invalid Format Error : The format of the specified data object is not valid.
In the error code documention, I see that this error could be caused by the following: The solution developer supplies an invalid HTML or OOXML string, a malformed HTML string, or an invalid OOXML string.
However, the body message needing to be displayed is a properly formatted HTML. I've even tried a regular string but still getting the same error.
The way I am calling it:
Office.context.mailbox.item.body.prependAsync(
'test',
{coercionType: Office.CoercionType.Html},
callback
)
Any advice is greatly appreciated. Thanks!
we have an integrated with google picker(read-only scope,Docs view) it use to work fine but recently some users are getting blank screens as soon as the pop up shows but when they select some filter everything starts working fine after that no problems.
using developer tools i see all apis returning 200 for that first request
but there were no docs in response(i believe this is the api responsible for bringing docs in picker 'https://docs.google.com/picker/pvr')
when there are no docs returned in above api google is calling another api i assume it is to log error's probably(//docs.google.com/picker/ohnoes)
this api has following error params in it
&error=Cached and requested query mismatch
&line=Not available
&viewToken=["all",null,{"query":null}]
&ms=97
&transferDocs=false
&numErrors=1
has anybody else faced the similar problem
what do error "Cached and requested query mismatch" means in context of drive docs
Fyi - most accounts facing this problem seems like are of company domain for ex "jondoe#company.org"(this is a google account with company domain)
Filters Image
Thanks for your help.
not sure but looks like issue was may be related to google bug
https://issuetracker.google.com/issues/64825685
for me the code that was not working was:
addView(google.picker.ViewId.DOCS)
replaced this code with below code which works as expected
var view = new google.picker.DocsView();
view.setIncludeFolders(true).setOwnedByMe(true).setParent('root');
addView(view).
i tried the basic example hosted on kendo mobile github:https://github.com/kendo-labs/kendo-plugins/tree/master/Mobile/IndexedListView
On local, works fine.
But i cant make it work on Icenium. I already ask them, but they recommend to ask around.
Kendo Music Store use this pluguin and works and i dont understand the difference.
Here the icenium proyect:
https://github.com/andrescolodrero/iceniumIndexedLIstView
Error:
:"Uncaught TypeError: Object [object Object] has no method '_scroller' "
IndexedListView is not yet updated to work with the latest Kendo UI Mobile (Q2 2013 and later). We plan to update it in the coming weeks.
The private method '_scroller' is now public 'scroller', changing this in the demo code would address that particular error, but there are other problems with the demo with Kendo UI Q2 2013. We're in the process of updating the demo and would ping back here, whenever it is done.
The webkit html notification (createHTMLNotification) work fine until yesterday. An error is appear (see below), the code has not change -> incompatible with the last version of chrome ?
Error message : Uncaught TypeError: Object #<NotificationCenter> has no method 'createHTMLNotification'
If I use the methode "createNotification", it's work fine but I need to use HTML notification.
The settings of chrome allowed the pop-up and notification for all website (and tests are in the code for check that).
Unfortunate, this feature has removed from chromium ...
see : https://plus.google.com/u/0/+GoogleChromeDevelopers/posts/8vWo8hq4pDm
http://developer.chrome.com/extensions/desktop_notifications.html
Warning: webKitNotifications.createHTMLNotification() in the web notifications API has been deprecated. The new web notifications API only allows text. Chrome notifications API will be promoted to stable soon and web notifications will be updated to use the new rich notifications format.
there is still hope.