Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[next] window.history.state getter throws exception #15371

Closed
DartBot opened this issue Nov 28, 2013 · 8 comments
Closed

[next] window.history.state getter throws exception #15371

DartBot opened this issue Nov 28, 2013 · 8 comments
Labels
area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. closed-obsolete Closed as the reported issue is no longer relevant library-html P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@DartBot
Copy link

DartBot commented Nov 28, 2013

This issue was originally filed by @bjornm


What steps will reproduce the problem?

import 'dart:html';

void main() {
  var x = window.history.state;
}

What is the expected output? What do you see instead?
no error. But it throws an error:

Breaking on exception: Unsupported operation: [info: ../../third_party/WebKit/Source/bindings/dart/custom/DartHistoryCustom.cpp:43]

What version of the product are you using? On what operating system?
30338. Mac OS X 10.7.5

Please provide any additional information below.

@kasperl
Copy link

kasperl commented Nov 29, 2013

Added Area-HTML, Triaged labels.

@kevmoo
Copy link
Member

kevmoo commented Apr 7, 2014

Removed Area-HTML label.
Added Area-Library, Library-Html labels.

@DartBot
Copy link
Author

DartBot commented Oct 1, 2014

This comment was originally written by tsk...@gmail.com


Same error as above on Windows 8 platform and Dart SDK version 1.7.0-dev.4.0. Saved state object in history but cannot get it back. History management cannot be implemented. Currently managing state object somewhere else, outside history object.

@DartBot
Copy link
Author

DartBot commented Oct 22, 2014

This comment was originally written by @Scorpiion


To complement the OS list, same issue occurs on Linux, Dart VM version: 1.7.2 (Tue Oct 14 06:55:59 2014) on "linux_x64".

@alan-knight
Copy link
Contributor

Dartium-only. May get fixed in the next rev.


Removed Priority-Unassigned label.
Added Priority-Medium label.
Changed the title to: "[next] window.history.state getter throws exception".

@anders-sandholm
Copy link
Contributor

Added C10 label.

@anders-sandholm
Copy link
Contributor

Alan, just wondering if there were any updates on this one?
I am tempted to make it M1.9 and "high".
WDYT?

@DartBot
Copy link
Author

DartBot commented Mar 21, 2015

This comment was originally written by mathieu.l...@gmail.com


Please =) !

The FIXME in the same cpp file, line 60, should probably be fixed in the same time.

All of this is needed for isomorphic apps, and very useful to implement a place system in a single page app (edit: the state is not so useful compared to a localstorage based solution : you actually still need to serialize).

@DartBot DartBot added Type-Defect area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. library-html labels Mar 21, 2015
@kevmoo kevmoo added P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed triaged labels Feb 29, 2016
@matanlurey matanlurey added the closed-obsolete Closed as the reported issue is no longer relevant label Jun 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. closed-obsolete Closed as the reported issue is no longer relevant library-html P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

6 participants