Why does a `click` event get triggered on my when I press Enter on it












6














I'm only adding a click event handler on my <button>.



HTML:



<button>Press <kbd>Enter</kbd> on me</button>


Javascript:



document.getElementsByTagName("button")[0].addEventListener("click", event => {

  event.preventDefault();



  console.log("Click:", event);

});


(Demo link)



Nevertheless, when I tab to the button in Firefox, then press Enter, I see the click event being fired. However, I cannot see this behaviour documented anywhere. Is this standard behaviour, and can I count on it working in all browsers?






javascript html dom accessibility dom-events







share|improve this question


















  • 1




    Try pressing the space bar when the button is in focus...another surprise..you clicked the button :-)
    – Thangadurai
    4 hours ago










  • Hehe yeah I got that, left it out for brevity :)
    – Vincent
    4 hours ago










  • keyboard geeks don't often use the mouse. Many even use vi-like addons to their browsers so that they can surf the web without ever touching their mouse. It's very frustrated when an app don't respond to keyboard events
    – phuclv
    26 mins ago
















6














I'm only adding a click event handler on my <button>.



HTML:



<button>Press <kbd>Enter</kbd> on me</button>


Javascript:



document.getElementsByTagName("button")[0].addEventListener("click", event => {

  event.preventDefault();



  console.log("Click:", event);

});


(Demo link)



Nevertheless, when I tab to the button in Firefox, then press Enter, I see the click event being fired. However, I cannot see this behaviour documented anywhere. Is this standard behaviour, and can I count on it working in all browsers?






javascript html dom accessibility dom-events







share|improve this question


















  • 1




    Try pressing the space bar when the button is in focus...another surprise..you clicked the button :-)
    – Thangadurai
    4 hours ago










  • Hehe yeah I got that, left it out for brevity :)
    – Vincent
    4 hours ago










  • keyboard geeks don't often use the mouse. Many even use vi-like addons to their browsers so that they can surf the web without ever touching their mouse. It's very frustrated when an app don't respond to keyboard events
    – phuclv
    26 mins ago














6












6








6







I'm only adding a click event handler on my <button>.



HTML:



<button>Press <kbd>Enter</kbd> on me</button>


Javascript:



document.getElementsByTagName("button")[0].addEventListener("click", event => {

  event.preventDefault();



  console.log("Click:", event);

});


(Demo link)



Nevertheless, when I tab to the button in Firefox, then press Enter, I see the click event being fired. However, I cannot see this behaviour documented anywhere. Is this standard behaviour, and can I count on it working in all browsers?






javascript html dom accessibility dom-events







share|improve this question













I'm only adding a click event handler on my <button>.



HTML:



<button>Press <kbd>Enter</kbd> on me</button>


Javascript:



document.getElementsByTagName("button")[0].addEventListener("click", event => {

  event.preventDefault();



  console.log("Click:", event);

});


(Demo link)



Nevertheless, when I tab to the button in Firefox, then press Enter, I see the click event being fired. However, I cannot see this behaviour documented anywhere. Is this standard behaviour, and can I count on it working in all browsers?






javascript html dom accessibility dom-events




javascript html dom accessibility dom-events






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 4 hours ago









Vincent

1,26211628




1,26211628








  • 1




    Try pressing the space bar when the button is in focus...another surprise..you clicked the button :-)
    – Thangadurai
    4 hours ago










  • Hehe yeah I got that, left it out for brevity :)
    – Vincent
    4 hours ago










  • keyboard geeks don't often use the mouse. Many even use vi-like addons to their browsers so that they can surf the web without ever touching their mouse. It's very frustrated when an app don't respond to keyboard events
    – phuclv
    26 mins ago














  • 1




    Try pressing the space bar when the button is in focus...another surprise..you clicked the button :-)
    – Thangadurai
    4 hours ago










  • Hehe yeah I got that, left it out for brevity :)
    – Vincent
    4 hours ago










  • keyboard geeks don't often use the mouse. Many even use vi-like addons to their browsers so that they can surf the web without ever touching their mouse. It's very frustrated when an app don't respond to keyboard events
    – phuclv
    26 mins ago








1




1




Try pressing the space bar when the button is in focus...another surprise..you clicked the button :-)
– Thangadurai
4 hours ago




Try pressing the space bar when the button is in focus...another surprise..you clicked the button :-)
– Thangadurai
4 hours ago












Hehe yeah I got that, left it out for brevity :)
– Vincent
4 hours ago




Hehe yeah I got that, left it out for brevity :)
– Vincent
4 hours ago












keyboard geeks don't often use the mouse. Many even use vi-like addons to their browsers so that they can surf the web without ever touching their mouse. It's very frustrated when an app don't respond to keyboard events
– phuclv
26 mins ago




keyboard geeks don't often use the mouse. Many even use vi-like addons to their browsers so that they can surf the web without ever touching their mouse. It's very frustrated when an app don't respond to keyboard events
– phuclv
26 mins ago












2 Answers
2






active

oldest

votes


















6














This is largely because lots of authors have historically written code using click events while forgetting to account for users who don't click (whether because they prefer to use a keyboard to navigate, have a disability which makes it hard to use a pointing device, or whatever other reason).



The behaviour is documented in the HTML specification:




Certain elements in HTML have an activation behavior, which means that the user can activate them. This triggers a sequence of events dependent on the activation mechanism, and normally culminating in a click event, as described below.



…



For accessibility, the keyboard’s Enter and Space keys are often used to trigger an element’s activation behavior.




It then goes on to explain the steps in detail.






share|improve this answer























  • That's great, thanks for the reference - I will be relying on that for accessibility then!
    – Vincent
    4 hours ago










  • It's a very useful mechanism. If you plan to rely on it for accessibility, the caveat is that most elements do not have this default behaviour, so if you're using (say) a div or a span as a control, you'll have to add the key event handling yourself. (Be sure to add a role attribute too!)
    – brennanyoung
    3 hours ago






  • 1




    @brennanyoung — And make them keyboard accessible with tabindex … best to use elements designed to be interacted with in the first place!
    – Quentin
    3 hours ago






  • 1




    Quite right. You get a lot of accessibility 'for free' with <a>, <input> and <button>, but otherwise tabindex is just as important. Unfortunately, a11y implementation is far too rarely considered 'in the first place'.
    – brennanyoung
    3 hours ago










  • I switched from an <a> to a <button> for exactly this reason - to make sure I get the browser's a11y features for free. With tabindex, role and click and keydown event handlers, I'm sure I'd probably still have forgotten something, or would implement something incorrectly :)
    – Vincent
    3 hours ago





















3














Because for keyboard users (where mouse is not available), when a button is in focus and you press enter (possibly space as well) it simulates a click event.



This is the browsers accessibility support which most if not all browsers provide.






share|improve this answer



















  • 1




    "It's part of the ISO" — It isn't … and nobody uses ISO HTML anyway.
    – Quentin
    4 hours ago










  • @Quentin Removed. You're right, our workplace puts a big importance on the ISO hence the reference.
    – Adriani6
    4 hours ago










  • Ah sorry, I did not mean "why did they make it this way", but "why did browsers implement this - was it because it was standardised, or because they thought it was a good idea themselves". Apparently the former!
    – Vincent
    4 hours ago










  • @Vincent – The standard was defined after most browsers had already implemented it.
    – Quentin
    4 hours ago










  • I see. Well, that's great for me - saves me implementing keypress handlers myself :)
    – Vincent
    4 hours ago











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54073140%2fwhy-does-a-click-event-get-triggered-on-my-button-when-i-press-enter-on-it%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









6














This is largely because lots of authors have historically written code using click events while forgetting to account for users who don't click (whether because they prefer to use a keyboard to navigate, have a disability which makes it hard to use a pointing device, or whatever other reason).



The behaviour is documented in the HTML specification:




Certain elements in HTML have an activation behavior, which means that the user can activate them. This triggers a sequence of events dependent on the activation mechanism, and normally culminating in a click event, as described below.



…



For accessibility, the keyboard’s Enter and Space keys are often used to trigger an element’s activation behavior.




It then goes on to explain the steps in detail.






share|improve this answer























  • That's great, thanks for the reference - I will be relying on that for accessibility then!
    – Vincent
    4 hours ago










  • It's a very useful mechanism. If you plan to rely on it for accessibility, the caveat is that most elements do not have this default behaviour, so if you're using (say) a div or a span as a control, you'll have to add the key event handling yourself. (Be sure to add a role attribute too!)
    – brennanyoung
    3 hours ago






  • 1




    @brennanyoung — And make them keyboard accessible with tabindex … best to use elements designed to be interacted with in the first place!
    – Quentin
    3 hours ago






  • 1




    Quite right. You get a lot of accessibility 'for free' with <a>, <input> and <button>, but otherwise tabindex is just as important. Unfortunately, a11y implementation is far too rarely considered 'in the first place'.
    – brennanyoung
    3 hours ago










  • I switched from an <a> to a <button> for exactly this reason - to make sure I get the browser's a11y features for free. With tabindex, role and click and keydown event handlers, I'm sure I'd probably still have forgotten something, or would implement something incorrectly :)
    – Vincent
    3 hours ago


















6














This is largely because lots of authors have historically written code using click events while forgetting to account for users who don't click (whether because they prefer to use a keyboard to navigate, have a disability which makes it hard to use a pointing device, or whatever other reason).



The behaviour is documented in the HTML specification:




Certain elements in HTML have an activation behavior, which means that the user can activate them. This triggers a sequence of events dependent on the activation mechanism, and normally culminating in a click event, as described below.



…



For accessibility, the keyboard’s Enter and Space keys are often used to trigger an element’s activation behavior.




It then goes on to explain the steps in detail.






share|improve this answer























  • That's great, thanks for the reference - I will be relying on that for accessibility then!
    – Vincent
    4 hours ago










  • It's a very useful mechanism. If you plan to rely on it for accessibility, the caveat is that most elements do not have this default behaviour, so if you're using (say) a div or a span as a control, you'll have to add the key event handling yourself. (Be sure to add a role attribute too!)
    – brennanyoung
    3 hours ago






  • 1




    @brennanyoung — And make them keyboard accessible with tabindex … best to use elements designed to be interacted with in the first place!
    – Quentin
    3 hours ago






  • 1




    Quite right. You get a lot of accessibility 'for free' with <a>, <input> and <button>, but otherwise tabindex is just as important. Unfortunately, a11y implementation is far too rarely considered 'in the first place'.
    – brennanyoung
    3 hours ago










  • I switched from an <a> to a <button> for exactly this reason - to make sure I get the browser's a11y features for free. With tabindex, role and click and keydown event handlers, I'm sure I'd probably still have forgotten something, or would implement something incorrectly :)
    – Vincent
    3 hours ago
















6












6








6






This is largely because lots of authors have historically written code using click events while forgetting to account for users who don't click (whether because they prefer to use a keyboard to navigate, have a disability which makes it hard to use a pointing device, or whatever other reason).



The behaviour is documented in the HTML specification:




Certain elements in HTML have an activation behavior, which means that the user can activate them. This triggers a sequence of events dependent on the activation mechanism, and normally culminating in a click event, as described below.



…



For accessibility, the keyboard’s Enter and Space keys are often used to trigger an element’s activation behavior.




It then goes on to explain the steps in detail.






share|improve this answer














This is largely because lots of authors have historically written code using click events while forgetting to account for users who don't click (whether because they prefer to use a keyboard to navigate, have a disability which makes it hard to use a pointing device, or whatever other reason).



The behaviour is documented in the HTML specification:




Certain elements in HTML have an activation behavior, which means that the user can activate them. This triggers a sequence of events dependent on the activation mechanism, and normally culminating in a click event, as described below.



…



For accessibility, the keyboard’s Enter and Space keys are often used to trigger an element’s activation behavior.




It then goes on to explain the steps in detail.







share|improve this answer














share|improve this answer



share|improve this answer








edited 4 hours ago

























answered 4 hours ago









Quentin

640k718611032




640k718611032












  • That's great, thanks for the reference - I will be relying on that for accessibility then!
    – Vincent
    4 hours ago










  • It's a very useful mechanism. If you plan to rely on it for accessibility, the caveat is that most elements do not have this default behaviour, so if you're using (say) a div or a span as a control, you'll have to add the key event handling yourself. (Be sure to add a role attribute too!)
    – brennanyoung
    3 hours ago






  • 1




    @brennanyoung — And make them keyboard accessible with tabindex … best to use elements designed to be interacted with in the first place!
    – Quentin
    3 hours ago






  • 1




    Quite right. You get a lot of accessibility 'for free' with <a>, <input> and <button>, but otherwise tabindex is just as important. Unfortunately, a11y implementation is far too rarely considered 'in the first place'.
    – brennanyoung
    3 hours ago










  • I switched from an <a> to a <button> for exactly this reason - to make sure I get the browser's a11y features for free. With tabindex, role and click and keydown event handlers, I'm sure I'd probably still have forgotten something, or would implement something incorrectly :)
    – Vincent
    3 hours ago




















  • That's great, thanks for the reference - I will be relying on that for accessibility then!
    – Vincent
    4 hours ago










  • It's a very useful mechanism. If you plan to rely on it for accessibility, the caveat is that most elements do not have this default behaviour, so if you're using (say) a div or a span as a control, you'll have to add the key event handling yourself. (Be sure to add a role attribute too!)
    – brennanyoung
    3 hours ago






  • 1




    @brennanyoung — And make them keyboard accessible with tabindex … best to use elements designed to be interacted with in the first place!
    – Quentin
    3 hours ago






  • 1




    Quite right. You get a lot of accessibility 'for free' with <a>, <input> and <button>, but otherwise tabindex is just as important. Unfortunately, a11y implementation is far too rarely considered 'in the first place'.
    – brennanyoung
    3 hours ago










  • I switched from an <a> to a <button> for exactly this reason - to make sure I get the browser's a11y features for free. With tabindex, role and click and keydown event handlers, I'm sure I'd probably still have forgotten something, or would implement something incorrectly :)
    – Vincent
    3 hours ago


















That's great, thanks for the reference - I will be relying on that for accessibility then!
– Vincent
4 hours ago




That's great, thanks for the reference - I will be relying on that for accessibility then!
– Vincent
4 hours ago












It's a very useful mechanism. If you plan to rely on it for accessibility, the caveat is that most elements do not have this default behaviour, so if you're using (say) a div or a span as a control, you'll have to add the key event handling yourself. (Be sure to add a role attribute too!)
– brennanyoung
3 hours ago




It's a very useful mechanism. If you plan to rely on it for accessibility, the caveat is that most elements do not have this default behaviour, so if you're using (say) a div or a span as a control, you'll have to add the key event handling yourself. (Be sure to add a role attribute too!)
– brennanyoung
3 hours ago




1




1




@brennanyoung — And make them keyboard accessible with tabindex … best to use elements designed to be interacted with in the first place!
– Quentin
3 hours ago




@brennanyoung — And make them keyboard accessible with tabindex … best to use elements designed to be interacted with in the first place!
– Quentin
3 hours ago




1




1




Quite right. You get a lot of accessibility 'for free' with <a>, <input> and <button>, but otherwise tabindex is just as important. Unfortunately, a11y implementation is far too rarely considered 'in the first place'.
– brennanyoung
3 hours ago




Quite right. You get a lot of accessibility 'for free' with <a>, <input> and <button>, but otherwise tabindex is just as important. Unfortunately, a11y implementation is far too rarely considered 'in the first place'.
– brennanyoung
3 hours ago












I switched from an <a> to a <button> for exactly this reason - to make sure I get the browser's a11y features for free. With tabindex, role and click and keydown event handlers, I'm sure I'd probably still have forgotten something, or would implement something incorrectly :)
– Vincent
3 hours ago






I switched from an <a> to a <button> for exactly this reason - to make sure I get the browser's a11y features for free. With tabindex, role and click and keydown event handlers, I'm sure I'd probably still have forgotten something, or would implement something incorrectly :)
– Vincent
3 hours ago















3














Because for keyboard users (where mouse is not available), when a button is in focus and you press enter (possibly space as well) it simulates a click event.



This is the browsers accessibility support which most if not all browsers provide.






share|improve this answer



















  • 1




    "It's part of the ISO" — It isn't … and nobody uses ISO HTML anyway.
    – Quentin
    4 hours ago










  • @Quentin Removed. You're right, our workplace puts a big importance on the ISO hence the reference.
    – Adriani6
    4 hours ago










  • Ah sorry, I did not mean "why did they make it this way", but "why did browsers implement this - was it because it was standardised, or because they thought it was a good idea themselves". Apparently the former!
    – Vincent
    4 hours ago










  • @Vincent – The standard was defined after most browsers had already implemented it.
    – Quentin
    4 hours ago










  • I see. Well, that's great for me - saves me implementing keypress handlers myself :)
    – Vincent
    4 hours ago
















3














Because for keyboard users (where mouse is not available), when a button is in focus and you press enter (possibly space as well) it simulates a click event.



This is the browsers accessibility support which most if not all browsers provide.






share|improve this answer



















  • 1




    "It's part of the ISO" — It isn't … and nobody uses ISO HTML anyway.
    – Quentin
    4 hours ago










  • @Quentin Removed. You're right, our workplace puts a big importance on the ISO hence the reference.
    – Adriani6
    4 hours ago










  • Ah sorry, I did not mean "why did they make it this way", but "why did browsers implement this - was it because it was standardised, or because they thought it was a good idea themselves". Apparently the former!
    – Vincent
    4 hours ago










  • @Vincent – The standard was defined after most browsers had already implemented it.
    – Quentin
    4 hours ago










  • I see. Well, that's great for me - saves me implementing keypress handlers myself :)
    – Vincent
    4 hours ago














3












3








3






Because for keyboard users (where mouse is not available), when a button is in focus and you press enter (possibly space as well) it simulates a click event.



This is the browsers accessibility support which most if not all browsers provide.






share|improve this answer














Because for keyboard users (where mouse is not available), when a button is in focus and you press enter (possibly space as well) it simulates a click event.



This is the browsers accessibility support which most if not all browsers provide.







share|improve this answer














share|improve this answer



share|improve this answer








edited 4 hours ago

























answered 4 hours ago









Adriani6

4,34421327




4,34421327








  • 1




    "It's part of the ISO" — It isn't … and nobody uses ISO HTML anyway.
    – Quentin
    4 hours ago










  • @Quentin Removed. You're right, our workplace puts a big importance on the ISO hence the reference.
    – Adriani6
    4 hours ago










  • Ah sorry, I did not mean "why did they make it this way", but "why did browsers implement this - was it because it was standardised, or because they thought it was a good idea themselves". Apparently the former!
    – Vincent
    4 hours ago










  • @Vincent – The standard was defined after most browsers had already implemented it.
    – Quentin
    4 hours ago










  • I see. Well, that's great for me - saves me implementing keypress handlers myself :)
    – Vincent
    4 hours ago














  • 1




    "It's part of the ISO" — It isn't … and nobody uses ISO HTML anyway.
    – Quentin
    4 hours ago










  • @Quentin Removed. You're right, our workplace puts a big importance on the ISO hence the reference.
    – Adriani6
    4 hours ago










  • Ah sorry, I did not mean "why did they make it this way", but "why did browsers implement this - was it because it was standardised, or because they thought it was a good idea themselves". Apparently the former!
    – Vincent
    4 hours ago










  • @Vincent – The standard was defined after most browsers had already implemented it.
    – Quentin
    4 hours ago










  • I see. Well, that's great for me - saves me implementing keypress handlers myself :)
    – Vincent
    4 hours ago








1




1




"It's part of the ISO" — It isn't … and nobody uses ISO HTML anyway.
– Quentin
4 hours ago




"It's part of the ISO" — It isn't … and nobody uses ISO HTML anyway.
– Quentin
4 hours ago












@Quentin Removed. You're right, our workplace puts a big importance on the ISO hence the reference.
– Adriani6
4 hours ago




@Quentin Removed. You're right, our workplace puts a big importance on the ISO hence the reference.
– Adriani6
4 hours ago












Ah sorry, I did not mean "why did they make it this way", but "why did browsers implement this - was it because it was standardised, or because they thought it was a good idea themselves". Apparently the former!
– Vincent
4 hours ago




Ah sorry, I did not mean "why did they make it this way", but "why did browsers implement this - was it because it was standardised, or because they thought it was a good idea themselves". Apparently the former!
– Vincent
4 hours ago












@Vincent – The standard was defined after most browsers had already implemented it.
– Quentin
4 hours ago




@Vincent – The standard was defined after most browsers had already implemented it.
– Quentin
4 hours ago












I see. Well, that's great for me - saves me implementing keypress handlers myself :)
– Vincent
4 hours ago




I see. Well, that's great for me - saves me implementing keypress handlers myself :)
– Vincent
4 hours ago


















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54073140%2fwhy-does-a-click-event-get-triggered-on-my-button-when-i-press-enter-on-it%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

CARDNET

Image
CARDNET は日本カードネットワークが運営するクレジット決済ネットワーク。日本カードネットワークの略称としてもCARDNETが使用されている。 事件・事故 2017年4月15日午前11時8分からクレジットカードの決済がしづらくなる障害が発生した。障害は同日午後5時18分に復旧した。原因は、複数あるCARDNETセンターの拠点のうち1つで、2重化してあるL3スイッチの片方が故障し、1系統にトラフィックが集中したことによる輻輳が発生したため。対処としては、故障したL3スイッチ交換とシステム再起動が行われた [1] 。 出典 ^ 金子寛人 ( 2017年4月17日 ). “CARDNETのクレジット決済に6時間強障害、原因はL3スイッチ故障”. 日経コンピュータ. 2018年10月18日 閲覧。 この項目は、コンピュータに関連した 書きかけの項目 です。この項目を加筆・訂正などしてくださる協力者を求めています（PJ:コンピュータ/P:コンピュータ）。 この項目は、経済に関連した 書きかけの項目 です。この項目を加筆・訂正などしてくださる協力者を求めています（ポータル 経済学、プロジェクト 経済）。 This page is only for reference, If you need detailed information, please check here
Read more

Boot-repair Failure: Unable to locate package grub-common:i386

Image
0 I am on a system dual-booting Windows and Debian (usually using the latter), and a recent Windows update appears to have wreaked havoc on the Debian boot system. I managed to boot Windows again, but not Linux. Following online suggestions, I created a Live USB of Ubuntu, and booted from that. Then I have installed and run the boot-repair utility. The utility instructs me to type several lines including sudo chroot "/mnt/boot-sav/sda6" apt-get purge -y grub*-common grub-common:i386 To which I receive the error E: Unable to locate package grub-common:i386 I am given to understand the issue may have to do with having UEFI vs BIOS (I believe I have UEFI), but do not understand this well. In any case I have subsequently run the boot-repair BootInfo Summary utility which created the following file h
Read more

濃尾地震

Image
濃尾地震 『岐阜市街大地震之図』 歌川国利画 本震 発生日 1891年（明治24年）10月28日 発生時刻 6時38分50秒（JST） 震央 日本 岐阜県本巣郡西根尾村（現・本巣市） 北緯35度35分 東経136度20分（ 地図 ） 規模    マグニチュード（M）8.0 最大震度    震度7： 注1 福井県今立郡鯖江町、愛知県葉栗郡大田島村、東春日井郡勝川村 地震の種類 直下型地震 被害 死傷者数 死者7,273人、負傷者17,175人 注1：当時の震度階級では「激烈」 プロジェクト:地球科学 プロジェクト:災害 テンプレートを表示 濃尾地震 （のうびじしん）は、1891年（明治24年）10月28日に濃尾地方で発生した、日本史上最大の内陸地殻内地震。「 美濃・尾張地震 （みの・おわりじしん）」とも呼ばれている。辛卯の年に発生したことから 辛卯震災 と呼んでいる報告書もある。 目次 1 概要 1.1 震源断層 2 被害 3 各地の震度 4 前兆現象 5 報道 6 学術的な意義 7 地震防災 8 脚注 9 関連項目 10 外部リンク 概要 濃尾地震発生当時の根尾谷断層 濃尾地震を引き起こした根尾谷断層 写真中央を斜めに走る段差が根尾谷断層 濃尾地震は、1891年10月28日6時38分50秒に発生した。震源は、岐阜県本巣郡西根尾村（現・本巣市）、北緯35度35分、東経136度20分付近。河角廣 (1951) は岐阜市付近（北緯35.6度、東経136.6度）に震央を仮定し規模 M K = 7.0 を与え [1] 、マグニチュードは M = 8.4 に換算されているが、明治・大正期の地震については0.5程度大きく見積もられているとされる [2] 。また、震央距離と震度との関係など当時のデータから後にM8.0 [3] とも推定される。アメリカ地質調査所 (USGS) でも8.0としている [4] 。「根尾谷断層帯」が活動した典型的な内陸地殻内地震（いわゆる直下型地震）であり、これは記録が残っている日本の内陸
Read more